DOMly
DOMly copied to clipboard
lazd
The fast template system that creates and clones DOM nodes
Current version of DOMly is vulnerable as you can see in this report : https://snyk.io/test/github/lazd/DOMly This issue is about fixing those vulnerabilities. (Could be similar to https://github.com/lazd/DOMly/issues/34)
``` html {{Coral.i18n.get("English string: {0}", 25)}} ``` Results in: ``` Warning: Function.prototype.toString is not generic ```
In order for users to know which elements were created by DOMly, it should be possible to add a marker attribute to every generated element. This allows users to perform...
Input file: ``` html body { color: green } ``` Result: ``` Error: Parse error on line 2: body { color: green } -------^ Expecting 'EOF', 'ESCAPED_LEFT', 'ESCAPED_RIGHT', 'CONTENT', '{{',...
I test it just if compiles, not integrated in a project, yet. https://github.com/Shimballa/node-domlyfy ``` "browserify": { "transform": [ [ "domlyfy", { "precompilerOptions": { "stripWhitespace": true } } ] ] }...
Expressions should be allowed in statements: 1. `{{variable+1}}` 2. `{{variable+method()}}` 3. `{{method(variable+otherVariable)}}` 4. ``
I can create a patch - but would like to know if this has any chance. I am working in a project that is undergoing a change towards DOMly and...
From the description, it looks like DOMly's pre-compiled templates will work on IE8 and above (based on info about the use of `createElement`, `DocumentFragment` and `Node`). Is this assumption correct?...
The output is less than ideal when `\{` and `\}` are present -- there is additional string concatenation going on in the compiled function that is pretty ugly: Template: ```...
Currently, only `if-prop` attributes are supported and the same conditional must be repeated as `unless-prop` for the `else` block. It would be nice to have `else` statements somehow.