Frontend Validation

[rak-phillip]

Validating inputs is a topic that has been raised multiple times in the past ¹, yet we still don't have a solution for this problem. I think it would make sense to settle on an approach.

Why do we need a validation library

Rancher Desktop has multiple patterns for conveying invalid values in inputs. We can improve by applying a consistent design.

Examples

Validation Libraries

Utilizing existing validation libraries can simplify the task of adding validation to existing forms, allowing us time to focus on the design and UX of validation messages. Some popular validation libraries for vue include

• Vuelidate
• VeeValidate

Footnotes

1. https://github.com/rancher-sandbox/rancher-desktop/pull/2579#discussion_r926930482 ↩

[ericpromislow]

I would expect that the messages users get via the API or rdctl would be consistent with messages in the UI

[jandubois]

I would expect that the messages users get via the API or rdctl would be consistent with messages in the UI

Does this means the validation needs to happen in the backend? Maybe this can simply piggyback on the proposeSettings API to validate all the settings as well?

[jandubois]

Issue #2540 has more details about various validations.

[gaktive]

@torchiaf to look at the validation libraries to see if they can help us out here.