When I set a pagination ID returns Syntax Error: Token '__currentPage' is an unexpected token at column 4 of the expression [184__currentPage] starting at [__currentPage].
See original GitHub issueHello, I am working on a page with different bootstrap tabs. Each tab has it’s own pagination so I need to have one dir-paginate for each tab. I have dir-paginate inside a ng-repeat, but when It comes to define the pagination-id it throws me this error: Syntax Error: Token ‘__currentPage’ is an unexpected token at column 4 of the expression [184__currentPage] starting at [__currentPage].
This is my code:
`<div class="tab-pane" ng-repeat="protocolo in getMezclasAdministracion.Object" id="protocolo-{{ protocolo.Codigoprotocolo }}">
Thank you
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Syntax Error: Token 'em' is an unexpected token at column 4 ...
Im getting this error [$parse:syntax] Syntax Error: Token 'em' is an unexpected token at column 4 of the expression [it em.divider] starting ......
Read more >REST API Developer Guide
HTTP Authorization—Provides the OAuth 2.0 access token to authorize your client. REST API supports the Bearer authentication.
Read more >The JasperReports Ultimate Guide Third Edition
in the resulting expression, and no attempt to parse the token is made ... setting and there is not enough space on the...
Read more >Untitled
46590, Defect, Query, Ancestry Columns use the wrong ID for URLs ... 40506, Defect, Portal, Uncaught SyntaxError: Unexpected token '-' on root projects...
Read more >Hibernate Search 6.1.7.Final: Reference Documentation
Once the data is indexed, you can perform search queries. The following code will prepare a search query targeting the index for the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@michaelbromley issue solved!
Hi, In v0.11.0 I introduced a change that fixes a fairly serious memory leak. It looks like it was too aggressive in the way it cleans up references and there are a couple of issues now - this included - where things break when the pagination is inside a directive that dynamically destroys DOM (e.g. ngIf, ngRepeat)
For now, just use 0.10.1 - unless you need template strings (also introduced in 0.11.0), you are not missing out on anything new. I will fix this as soon as I get some time to invest.