-
Notifications
You must be signed in to change notification settings - Fork 29
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
Expression and Dataformat Metadata editing - might omit form field #904
Labels
bug
Something isn't working
canvas/config-form
Configuration form related issues
ui/ux
This issue is about improving the UI / UX
Milestone
Comments
Since potentially the expression could be a different syntax, one thing to consider is whether we want to preserve the ID and the expression field. |
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 8, 2024
When the users includes config in a form field, which has same name as form field of another language/dataformat type, to which they can switch - the previously configured form field might get omited. The fix is to assign a key to the form, so React know that the form should be recreated without reusing the existing fields. fix: KaotoIO#904
lordrip
added a commit
to lordrip/kaoto
that referenced
this issue
Mar 11, 2024
When the users includes config in a form field, which has same name as form field of another language/dataformat type, to which they can switch - the previously configured form field might get omited. The fix is to assign a key to the form, so React know that the form should be recreated without reusing the existing fields. fix: KaotoIO#904
As pointed out by @tplevko, apart from the |
lordrip
added a commit
that referenced
this issue
Mar 12, 2024
When the users includes config in a form field, which has same name as form field of another language/dataformat type, to which they can switch - the previously configured form field might get omited. The fix is to assign a key to the form, so React know that the form should be recreated without reusing the existing fields. fix: #904
tplevko
pushed a commit
to tplevko/kaoto-next
that referenced
this issue
Mar 12, 2024
When the users includes config in a form field, which has same name as form field of another language/dataformat type, to which they can switch - the previously configured form field might get omited. The fix is to assign a key to the form, so React know that the form should be recreated without reusing the existing fields. fix: KaotoIO#904
tplevko
pushed a commit
to tplevko/kaoto-next
that referenced
this issue
Mar 12, 2024
When the users includes config in a form field, which has same name as form field of another language/dataformat type, to which they can switch - the previously configured form field might get omited. The fix is to assign a key to the form, so React know that the form should be recreated without reusing the existing fields. fix: KaotoIO#904
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
canvas/config-form
Configuration form related issues
ui/ux
This issue is about improving the UI / UX
Describe the Bug
When the users includes config in a form field, which has same name as form field of another language/dataformat type, to which they can switch - the previously configured form field might get omited.
Steps to Reproduce the Bug or Issue
Screenshots or Videos
vokoscreenNG-2024-03-05_13-34-01.webm
Platform
The text was updated successfully, but these errors were encountered: