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

custom token definitions? #54

Closed
icai opened this issue Dec 30, 2017 · 1 comment
Closed

custom token definitions? #54

icai opened this issue Dec 30, 2017 · 1 comment

Comments

@icai
Copy link

icai commented Dec 30, 2017

I want to use part of front end template and use part of back end template.
so catch the token definition rended!
open {{
close }}

I want to chang to
open: '<%=',
close: '%>'


or use raw block to render?

@harttle
Copy link
Owner

harttle commented Dec 30, 2017

It'll be a useful feature.

Most (if not all) lexical parsing is located at src/tokenizer.js, it should be easy to provide options to re-define the syntax for outputs and tags. PR is wellcome, I can help make it running.

harttle pushed a commit that referenced this issue Feb 20, 2019
# [7.2.0](v7.1.0...v7.2.0) (2019-02-20)

### Features

* override output/tag delimiter, fixes [#54](#54) ([d20a043](d20a043))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants