Skip to content

Conversation

vsavkin
Copy link
Contributor

@vsavkin vsavkin commented Nov 3, 2015

BREAKING CHANGE

Previously, the controlsErrors getter of ControlGroup and ControlArray returned the errors of their direct children. This was confusing because the result did not include the errors of nested children (ControlGroup -> ControlGroup -> Control). Making controlsErrors to include such errors would require inventing some custom serialization format, which applications would have to understand.

Since controlsErrors was just a convenience method, and it was causing confusing, we are removing it. If you want to get the errors of the whole form serialized into a single object, you can manually traverse the form and accumulate the errors. This way you have more control over how the errors are serialized.

@vsavkin vsavkin added the action: review The PR is still awaiting reviews from at least one requested reviewer label Nov 3, 2015
@vsavkin vsavkin added this to the beta-00 milestone Nov 4, 2015
@matsko
Copy link
Contributor

matsko commented Nov 5, 2015

LGTM

@mary-poppins
Copy link

Merging PR #5102 on behalf of @vsavkin to branch presubmit-vsavkin-pr-5102.

@vsavkin vsavkin added the action: merge The PR is ready for merge by the caretaker label Nov 5, 2015
@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Nov 5, 2015
BREAKING CHANGE

Previously, the controlsErrors getter of ControlGroup and ControlArray returned the errors of their direct children. This was confusing because the result did not include the errors of nested children (ControlGroup -> ControlGroup -> Control). Making controlsErrors to include such errors would require inventing some custom serialization format, which applications would have to understand.

Since controlsErrors was just a convenience method, and it was causing confusing, we are removing it. If you want to get the errors of the whole form serialized into a single object, you can manually traverse the form and accumulate the errors. This way you have more control over how the errors are serialized.
@vsavkin vsavkin force-pushed the remove_control_errors branch from c2d923c to 42cfa3c Compare November 6, 2015 01:46
@vsavkin vsavkin added the action: merge The PR is ready for merge by the caretaker label Nov 6, 2015
@mary-poppins
Copy link

Merging PR #5102 on behalf of @vsavkin to branch presubmit-vsavkin-pr-5102.

@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Nov 6, 2015
@vsavkin vsavkin closed this in 7343ef0 Nov 6, 2015
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: review The PR is still awaiting reviews from at least one requested reviewer cla: yes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants