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

Content.json should be optional #6

Open
joeyfigaro opened this issue Jan 20, 2017 · 2 comments
Open

Content.json should be optional #6

joeyfigaro opened this issue Jan 20, 2017 · 2 comments

Comments

@joeyfigaro
Copy link

The project I'm working on is not relying on the compiler for inserting dynamic data, so we don't need config files for our templates. It'd be great if the compiler left {{ data }} tokens untouched (ready for being replaced later in the chain) if there was no config available for the template.

@maxlapides
Copy link
Owner

maxlapides commented Jan 20, 2017

that's a good idea! in the meantime, you can put those {{ data }} strings in the content.json file.

example handlebars:

<h1>{{ headline }}</h1>

example content.json:

{
    headline: "{{ data }}"
}

i know this is kind of annoying! i'll think about a better long-term solution.

@joeyfigaro
Copy link
Author

That's a great suggestion @maxlapides - thanks! Could be much worse, and totally takes care of what we need for the time being.

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