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

Windows doesn't allow parentheses in path #40

Open
Arteneko opened this issue Feb 7, 2020 · 5 comments
Open

Windows doesn't allow parentheses in path #40

Arteneko opened this issue Feb 7, 2020 · 5 comments

Comments

@Arteneko
Copy link
Contributor

Arteneko commented Feb 7, 2020

Following #39, I tried to use the date thingy to auto-date my articles, but it seems like () isn't a windows-compatible path character.

auto-date

@Keats
Copy link
Owner

Keats commented Feb 7, 2020

Hmm I don't think calling functions in filenames was meant to be allowed, it's extremely niche.

@Arteneko
Copy link
Contributor Author

Arteneko commented Feb 8, 2020

So uh, what about, as an alternative, aliases?

Like, you could define an alias for a given template in your template.toml and reuse that alias?

That would effectively fix every character problem that currently exists, and would be a fairly simple first-step treatment.

What do you think of that?

@Keats
Copy link
Owner

Keats commented Feb 8, 2020

Hmm I'm not sure about that, it seems that it would make the content/configuration way more complex for some very nich usecases: templates are not rendered from what you see, you need to check the config file to know what it's going to be.

@Arteneko
Copy link
Contributor Author

I just thought about something.

Can we use Tera in defaults?

That would allow to execute the function / filter combo, and I'd just need to skip the question.

@Keats
Copy link
Owner

Keats commented Feb 12, 2020

I thought it was a great idea initially but I've changed my mind a bit.
This opens people expecting to be able to use other variables in default expressions which might be amazing but I can't really of a usecase where I wouldn't just put the filters/fn in the files directly. That only leaves filenames/directories which we cover for basic filters without arguments not more complex/functions. I don't know if it's worth the complexity

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

No branches or pull requests

2 participants