Description
Description
Description:
Currently, in the Cloudscape PropertyFilter component, after a user selects a property and an operator, the value field beside the operator allows free text typing, even when a custom form is provided for value entry. This allows users to bypass custom validation and logic implemented in the custom form, leading to inconsistent or invalid filter tokens.
Use Case:
We have scenarios where the value for a filter must be selected or validated through a custom form (e.g., dropdown, multiselect, or date picker). Allowing users to type arbitrary values directly into the inline value field beside the operator defeats the purpose of custom validation and can result in invalid or unsupported filter tokens.
Requested Feature:
Please provide a way (such as a prop or configuration option) to disable or hide the inline free text value input beside the operator in the PropertyFilter token editor, so that users are required to enter values only through the provided custom form.
Benefit:
This feature would ensure that all filter values are validated and consistent, improving data integrity and user experience. It would also allow developers to fully control the value entry process for each property/operator combination.
Code of Conduct
- I agree to follow this project's Code of Conduct
- I checked the current issues for duplicate requests