FIX associate converter parameter labels with their controls - #2513
Open
Alireza Aminzadeh (alireza-aminzadeh) wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Fixes #2506. Converter parameter fields now use Fluent
Fieldso the visible name is the accessible name for text, boolean, choice, and file controls. Required, error, and type hint stay attached to the same field.Tests and Documentation
ConverterParams.test.tsxrole/name coverage for the four control variants.npx jest src/components/Chat/ConverterPanel/ConverterParams.test.tsx src/components/Chat/ConverterPanel.test.tsx --no-coverage(53 passed)Made with Cursor