A way to validate hidden input with client side #364
Closed
Forus-Spec
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Hi @Forus-Spec, this will be resolved in the next version. The issue you see is caused by the usage of We are migrating to a context approach going forward. For details you can see this RFC and also test out the hidden input support using the pre-release version. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Conform Team,
I've been using Conform and find it amazing! I have a suggestion for a feature that could enhance its functionality. Currently, Conform does a great job of validating visible inputs, but I was wondering if there could be a possibility of extending this validation to hidden inputs as well.
Here's the scenario I encountered: I have a use case where I fetch data from a combobox, and upon selecting an item, I default hidden inputs to specific values. Essentially, I have a Fieldset that holds two properties:
If the user selects something, these values are automatically populated:
__ simplification for a mental model __
If the user select an item through combobox given options:
If the user doesn't select anything and just enters random values, it might look like this:
The issue arises because the item name input can be anything, and it didn't get picked from valid options
I understand that there might be various solutions to this problem
but I prefer this one as it aligns with the principles of progressive enhancement.
Adding a feature to Conform or pathway that allows for the validation of hidden inputs in client side
would greatly enhance its flexibility and usefulness in scenarios like the one I described.
I appreciate your ongoing efforts Conform.
Beta Was this translation helpful? Give feedback.
All reactions