-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployed apps don't reevaluate cells marked as 'Reevaluates automatically' #2568
Comments
@jonatanklosko do you remember why we disable reevaluate automatically for apps? I think it makes sense to keep due to the input behaviour, no? |
@josevalim it may have been a side effect, we first had automatic reevaluation for everything (#1928), so we skipped the logic for "automatically reevaluating" cells, and then we reverted to reevaluate changes with a button (#2066), but the "automatically reevaluating" logic is still skipped. I don't remember nor couldn't find if we actually discussed "automatically reevaluating" cells specifically. So with that context, I think it's fine to allow them. It should cover some of the use cases where reevaluating manually is awkward. And it's optional, so it doesn't break the use cases where we want to avoid eager reevaluation. Hopefully it's not confusing to have yet another behaviour in the equation, but in terms of consistency it probably makes sense. |
@josevalim perhaps initially we said that "automatically reevaluating" doesn't apply to apps and just rolled with it. Anyway, I'm ok making the change, wdyt? |
Agreed. I also think we forgot about the input cases and I would reenable it :) |
Thanks! This small change will make much easier to deploy prototype web apps 🙏 |
Environment
git rev-parse HEAD
if running with mix): v0.12.1Current behavior
Deployed apps don't reevaluate cells marked as 'Reevaluates automatically'.
For instance, in this example, when selecting a new entry in the dropdown menu in the deployed app, the following cell is not evaluated automatically.
However, it's the case when the entry is changed in Livebook (thus, not in deployed apps).
Expected behavior
I would expect the cells to be reevaluated automatically to offer a consistent experience.
The text was updated successfully, but these errors were encountered: