Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow bypassing html_escaping #81

Closed
wants to merge 1 commit into from

Conversation

mistercrunch
Copy link

In some cases mustache/chevron can be used to template strings that
are not html, for example templating SQL or other languages/strings like
markdown.

In some cases mustache/chevron can be used to template strings that
are not html, for example templating SQL or other languages/strings like
`markdown`.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling ebdd476 on mistercrunch:no_escape into 78f1a38 on noahmorrison:master.

@dcmoore-gd
Copy link

Would the existing {{{ ... }}} syntax not be sufficient for those use cases?

@mistercrunch
Copy link
Author

Oh. {{{ ... }}} is a great workaround for us that I wasn't aware off, though html-escaping in our context never makes any sense and not using it should be more the rule than the exception. I think that's true of all templating use-cases that are not targeting HTML.

@mistercrunch
Copy link
Author

closes #79

@noahmorrison
Copy link
Owner

I'm going to reject this in favor of using the triple brackets, which is what the spec recommends.

I'm not horrendously opposed to implementing this, it just seems unnecessary. Maybe I'll add a non-html mode later on if there's more community desire for such a mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants