Pr parameter fixes #363
Merged
Pr parameter fixes #363
Conversation
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
Collaborator
Author
|
Since none of this code effects anything in the pr checklist, I didn't go through it. |
lizlooney
requested changes
Dec 27, 2025
…face into pr_parameter_fixes
This adds the custom piece to FieldDropdown so it is shared between jump to step and get parameter blocks
lizlooney
approved these changes
Jan 1, 2026
Collaborator
lizlooney
left a comment
lizlooney
left a comment
There was a problem hiding this comment.
Very nice! Thank you!
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.
Fixes #293 (Adding a drop down to parameters)
Fixes #295 (Deleting a used parameter should flag where that parameter is being used as an error)