Skip to content
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

Display error messages for VariablesMapping (DMN/Objects API prefill) #4871

Open
stevenbal opened this issue Nov 29, 2024 · 0 comments · May be fixed by #5030
Open

Display error messages for VariablesMapping (DMN/Objects API prefill) #4871

stevenbal opened this issue Nov 29, 2024 · 0 comments · May be fixed by #5030

Comments

@stevenbal
Copy link
Contributor

From #4696 (comment)

The VariableMapping component currently doesn't show error messages that are passed to it (both for DMN configuration and Objects API prefill

@joeribekker joeribekker added this to the Release 3.0 milestone Dec 2, 2024
@robinmolen robinmolen moved this from Todo to In Progress in Development Jan 15, 2025
robinmolen added a commit that referenced this issue Jan 16, 2025
Because the inputs in the variable mapping don't have inline labels, the errorlist placement doesn't have to be compensated.
robinmolen added a commit that referenced this issue Jan 16, 2025
Normally, when the formRow or a child component receives errors, the 'errors' classname is added. This in turn adds basic "error" styling to the underlying inputs.

In situations where multiple inputs are placed in 1 FormRow, and 1 input receives an error, this results in all inputs showing error styling.
robinmolen added a commit that referenced this issue Jan 16, 2025
Ensure that the error messages for the DMN configuration are placed above the inputs
@robinmolen robinmolen linked a pull request Jan 22, 2025 that will close this issue
10 tasks
@robinmolen robinmolen linked a pull request Jan 22, 2025 that will close this issue
10 tasks
robinmolen added a commit that referenced this issue Jan 22, 2025
Because the inputs in the variable mapping don't have inline labels, the errorlist placement doesn't have to be compensated.
robinmolen added a commit that referenced this issue Jan 22, 2025
Normally, when the formRow or a child component receives errors, the 'errors' classname is added. This in turn adds basic "error" styling to the underlying inputs.

In situations where multiple inputs are placed in 1 FormRow, and 1 input receives an error, this results in all inputs showing error styling.
robinmolen added a commit that referenced this issue Jan 22, 2025
Ensure that the error messages for the DMN configuration are placed above the inputs
@robinmolen robinmolen moved this from In Progress to Implemented in Development Jan 23, 2025
robinmolen added a commit that referenced this issue Jan 29, 2025
Because the inputs in the variable mapping don't have inline labels, the errorlist placement doesn't have to be compensated.
robinmolen added a commit that referenced this issue Jan 29, 2025
Normally, when the formRow or a child component receives errors, the 'errors' classname is added. This in turn adds basic "error" styling to the underlying inputs.

In situations where multiple inputs are placed in 1 FormRow, and 1 input receives an error, this results in all inputs showing error styling.
robinmolen added a commit that referenced this issue Jan 29, 2025
Ensure that the error messages for the DMN configuration are placed above the inputs
robinmolen added a commit that referenced this issue Jan 29, 2025
Ensure that the error messages for the DMN configuration are placed above the inputs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Implemented
Development

Successfully merging a pull request may close this issue.

4 participants