Skip to content

docs(guide/expression): add clarification for RegExp literal in `ngPa… #5

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 6, 2017
Merged

docs(guide/expression): add clarification for RegExp literal in `ngPa… #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/content/guide/expression.ngdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,8 @@ AngularJS expressions are like JavaScript expressions with the following differe
even inside `ng-init` directive.

* **No RegExp Creation With Literal Notation:** You cannot create regular expressions
in an AngularJS expression.
in an AngularJS expression. An exception to this rule is {@link ngPattern `ng-pattern`} which accepts valid
RegExp.

* **No Object Creation With New Operator:** You cannot use `new` operator in an AngularJS expression.

Expand Down