-
Notifications
You must be signed in to change notification settings - Fork 899
feat: setup url autofill for dynamic parameters #17739
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
4209d7d
feat: setup autofill for dynamic parameters
jaaydenh 1d798ea
chore: cleanup
jaaydenh 9d10195
feat: set initial param values from autofill
jaaydenh ec35a7f
fix: setup ParameterLabel to use htmlfor
jaaydenh 04c7f83
chore: change autofill to boolean
jaaydenh 03dde8a
chore: updates for PR review comments
jaaydenh afdab85
chore: move logic for sending initial parameters to websocket
jaaydenh a76159f
fix: improvements to dynamic parameter handling
jaaydenh 6711e28
fix: updates for PR review
jaaydenh 7dc96bb
fix: update logic for onMessage
jaaydenh eb413fb
fix: format
jaaydenh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
fix: improvements to dynamic parameter handling
- Loading branch information
commit a76159f21fd86449e67231ebe46d1f977baa0649
There are no files selected for viewing
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not 100% clear on why this is set up this way, or the nuances of what it's trying to do.
onInput
is mostly equivalent toonChange
(in fact, React made the historical mistake of breaking from the HTML spec, and patchingonChange
to be more likeonInput
). I don't think most React components ever need bothI'm guessing that at the very least, the handler is meant to make it so that the textarea only grows when we know for a fact that the user wants to interact with it. In which case, all of this logic can be moved into the
onChange
handler.But if the max height is being statically set to
700px
, maybe we could make it so that this change triggers in response to the firstonFocus
event?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved the code to onChange, onFocus does not work as expected.