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

docs(guide/expressions): clarify regexp literals usage in expressions #10030

Conversation

pkozlowski-opensource
Copy link
Member

Closes #10026

@@ -164,6 +164,12 @@ expression. The reason behind this is core to the Angular philosophy that applic
be in controllers, not the views. If you need a real conditional, loop, or to throw from a view
expression, delegate to a JavaScript method instead.

## No RegExp creation with literal notation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might change the sub-heading to something else, or maybe put this in an alert div somewhere instead

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's up to you though, basically looks okay

@caitp caitp added this to the 1.3.3 milestone Nov 12, 2014
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.

Lexer fails to parse regex literal: /\\/
3 participants