fix: don't error when writing UI elements values that already exist#8147
Merged
fix: don't error when writing UI elements values that already exist#8147
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
manzt
approved these changes
Feb 5, 2026
|
🚀 Development release published. You may be able to view the changes at https://marimo.app?v=0.19.8-dev40 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since we now pre-populate the UI with the previous session, this adds/registers previous ui-elements. On refresh, we restore the values with the previous
ui_values. Previously we would throw if they already existed, but now this is expected.