Provide non-decoded text to parse consumers
#2714
Comments
colincasey
added a commit
to colincasey/svelte
that referenced
this issue
May 28, 2019
* master: (87 commits) -> v3.4.3 always add raw property to text nodes flesh out in/out transition tutorial chapter (sveltejs#2792) code style fix test fix tests Fix CRUD example to allow changing input values. Fixes sveltejs#2714 treat requestAnimationFrame as a noop on the server site: actions tutorial: destroy is not required (sveltejs#2776) Allow binding of <details> open site: add /faq redirect to GitHub wiki FAQ fix case sensitive import name, improve tsconfig type declarations for bundled files convert everything to TypeScript check for unknown props when creating component cleanup, improve comments typecheck npm script workarond for estree-walker related typings conflict compile/render-dom and other remaining typings ... # Conflicts: # src/compile/render-dom/wrappers/Element/index.ts
colincasey
added a commit
to colincasey/svelte
that referenced
this issue
May 28, 2019
…ings * master: (66 commits) -> v3.4.3 always add raw property to text nodes flesh out in/out transition tutorial chapter (sveltejs#2792) code style fix test fix tests Fix CRUD example to allow changing input values. Fixes sveltejs#2714 treat requestAnimationFrame as a noop on the server site: actions tutorial: destroy is not required (sveltejs#2776) Allow binding of <details> open site: add /faq redirect to GitHub wiki FAQ fix case sensitive import name, improve tsconfig type declarations for bundled files convert everything to TypeScript check for unknown props when creating component cleanup, improve comments typecheck npm script workarond for estree-walker related typings conflict compile/render-dom and other remaining typings ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently,
parsefromsvelte/compilerdecodes HTML entities (such as&or˙). This causes tools like prettier-plugin-svelte that use the AST to generate source text to write decoded entities back to the template. It would be nice if either this decoding happened later (after the parsing phase) or if an additional, non-decoded property was provided on text nodes.The text was updated successfully, but these errors were encountered: