feat(forms): add parseErrors to ControlValueAccessor for Signal Forms#67900
Closed
alxhub wants to merge 1 commit intoangular:mainfrom
Closed
feat(forms): add parseErrors to ControlValueAccessor for Signal Forms#67900alxhub wants to merge 1 commit intoangular:mainfrom
alxhub wants to merge 1 commit intoangular:mainfrom
Conversation
angular-robot
bot
added
detected: feature
Exposes parse errors when a UI control is used via Signal Forms. Parse errors occur when a user enters a value into a UI control that cannot be parsed into the target model type. The ControlValueAccessor interface now includes an optional readonly parseErrors signal. Signal Forms (FormField) will read this signal if present and propagate it to the field state.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exposes parse errors when a UI control is used via Signal Forms. Parse errors occur when a user enters a value into a UI control that cannot be parsed into the target model type. The ControlValueAccessor interface now includes an optional readonly parseErrors signal. Signal Forms (FormField) will read this signal if present and propagate it to the field state.