This repository was archived by the owner on Apr 12, 2024. It is now read-only.
fix(required): correctly validate when required on non-input element …#16836
Merged
Narretz merged 2 commits intoangular:masterfrom Mar 6, 2019
Merged
fix(required): correctly validate when required on non-input element …#16836Narretz merged 2 commits intoangular:masterfrom
Narretz merged 2 commits intoangular:masterfrom
Conversation
…is surrounded by ngIf Closes angular#16830
gkalpak
reviewed
Feb 21, 2019
This was referenced Mar 4, 2019
Closed
Closed
Contributor
|
looks like, all checks are passed but not merged |
3 tasks
…lement is surrounded by ngIf
603f4eb to
2cdae38
Compare
petebacondarwin
approved these changes
Mar 6, 2019
This was referenced Mar 7, 2019
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
…is surrounded by ngIf
Closes #16830
I've also ran this change against the ngMaterial unit tests, the uiBootstrap unit tests, the ionic unit tests, and manually tested with uiSelect.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements
Other information: