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

feat: add Validation to/in Autocomplete control #3115

Open
VBTXDeveloper opened this issue Dec 30, 2024 · 1 comment
Open

feat: add Validation to/in Autocomplete control #3115

VBTXDeveloper opened this issue Dec 30, 2024 · 1 comment
Labels
v5 For the next major version

Comments

@VBTXDeveloper
Copy link

🙋 Feature Request

Using the Autocomplete control, we are dynamically setting required to "true" when a different control is populated.
This properly sets the requirement; you cannot submit the form when the control is empty. However, the field remains required and will not validate successfully, even after you select a value. It would be nice for the validation to properly accept a value and allow for submission.

This was reported as a Bug, but marked 'working as designed'. So I'm converting it to a feature request for future consideration.

🤔 Expected Behavior

When we select a value in the autocomplete control, it should no longer say that the field is required, and allow the form to submit.

😯 Current Behavior

Field fails validation, even after a selection is made.
Image

💁 Possible Solution

🔦 Context

We would like to have a an autocomplete control be required when another field is selected. The control should require a selection and validate properly.

💻 Examples

Examples provided in referenced Bug ticket.
Image

@microsoft-github-policy-service microsoft-github-policy-service bot added the triage New issue. Needs to be looked at label Dec 30, 2024
@dvoituron
Copy link
Collaborator

Indeed. This feature is not yet implemented, as described in the doc.

I don't think we'll have time to develop it before v5. You have to handle this exception manually.

image

@vnbaaij vnbaaij added v5 For the next major version and removed triage New issue. Needs to be looked at labels Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v5 For the next major version
Projects
None yet
Development

No branches or pull requests

3 participants