Angular: RegExp Literal in template expression parse error

Created on 12 Jan 2016  ·  3Comments  ·  Source: angular/angular 
<div *ng-if="myStringVar.match(/regexp/)">myStringVar had 'regexp' in it! </div>`

produces 

EXCEPTION: Template parse errors:
Parser Error: Unexpected token / at column 25 in [ng-if myStringVar.match(/regexp/)] in function () {
 > div:nth-child(0)[*ng-if=myStringVar.match(/regexp/)]

in Chrome on Angular 2.0.0-alpha.46

Plunkr

core obvious
Source
picture wfalkwallace
👍1

Most helpful comment

...why?

picture wfalkwallace on 28 Sep 2016
👍15

All 3 comments

RegExp literal are not supported by the templating language.

They should be on your component.

vicb picture vicb on 26 Sep 2016

...why?

wfalkwallace picture wfalkwallace on 28 Sep 2016
👍15

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[bot] picture angular-automatic-lock-bot[bot] on 9 Sep 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

pkozlowski-opensource picture pkozlowski-opensource  ·  3Comments
vladimir-ivanov picture vladimir-ivanov  ·  3Comments
igorzg picture igorzg  ·  3Comments
andlcool picture andlcool  ·  3Comments
aquinum6 picture aquinum6  ·  3Comments