Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

docs(ngPattern): add note about using the g flag#11928

Closed
gkalpak wants to merge 1 commit into
angular:masterfrom
gkalpak:ngPattern-docs-avoid-g-flag
Closed

docs(ngPattern): add note about using the g flag#11928
gkalpak wants to merge 1 commit into
angular:masterfrom
gkalpak:ngPattern-docs-avoid-g-flag

Conversation

@gkalpak

@gkalpak gkalpak commented May 22, 2015

Copy link
Copy Markdown
Member

Add a note to point out that using the g flag on the validation RegExp, will cause each search to start at the index of the last search's match, thus not taking the whole input value into account.

Closes #11917
Closes #11928

Add a note to point out that using the `g` flag on the validation RegExp,
will cause each search to start at the index of the last search's match,
thus not taking the whole input value into account.

Closes angular#11917
Closes angular#11928
@gkalpak gkalpak force-pushed the ngPattern-docs-avoid-g-flag branch from 1260330 to 7c3b217 Compare May 22, 2015 14:17
@petebacondarwin

Copy link
Copy Markdown
Contributor

LGTM - please merge!

@gkalpak gkalpak closed this in 19ec993 May 22, 2015
@gkalpak gkalpak deleted the ngPattern-docs-avoid-g-flag branch May 22, 2015 19:24
netman92 pushed a commit to netman92/angular.js that referenced this pull request Aug 8, 2015
Add a note to point out that using the `g` flag on the validation RegExp,
will cause each search to start at the index of the last search's match,
thus not taking the whole input value into account.

Closes angular#11917
Closes angular#11928
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue with ng-pattern

3 participants