Comparing version 0.1.55 to 0.1.56
{ | ||
"name": "jangular", | ||
"version": "0.1.55", | ||
"version": "0.1.56", | ||
"description": "JavaScript based templating engine for Angular", | ||
@@ -5,0 +5,0 @@ "main": "lib/jangular.js", |
@@ -13,5 +13,2 @@ | ||
## Installation | ||
## Command Line Usage | ||
@@ -52,4 +49,8 @@ | ||
* -d or --data - The scope to use when you start evaluating. Either JSON or a path to a JSON or JS file | ||
* -s or --strip - When you include this option, all Angular directives will be stripped out of template after evaluating. See below for more explaination of why this is useful. | ||
* -s or --strip - When you include this option, all Angular binding directives will be stripped out of template after evaluating. | ||
The reason why strip is in there is that sometime you want the server side to | ||
produce HTML without any Angular binding directives so that when Angular bootstraps, it does | ||
not prematurally modify the rendered HTML. | ||
## Code Usage | ||
@@ -148,2 +149,10 @@ | ||
## Known Issues | ||
One thing is that if you use the {{ }} expression syntax, Jangular will replace the | ||
expression with the value. This may cause an issue if you are having the Angular | ||
client take over because Angular will just see the evaluated value and not the | ||
expression. For this reason, for now, we strongly suggest using ng-bind instead | ||
of {{ }} within inner HTML. | ||
## Pancakes | ||
@@ -150,0 +159,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
100008
178