Use key to force update when dynamic properties are changed #49
Conversation
This file contains 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
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.
As reported here https://discuss.streamlit.io/t/new-component-streamlit-keyup-a-textbox-that-returns-the-text-as-you-type/29860/9?u=blackary, changing the arguments to st_keyup doesn't actually affect the widget, except for the initial values passed when the widget is created.
This is rather ironic, given the purpose of this widget is to make a more dynamic version of st.text_input :)
This fixes this by making the key that is passed to the component depend on those arguments, so that if you pass a new value, the widget gets re-rendered with those new arguments.