-
Notifications
You must be signed in to change notification settings - Fork 104
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
Make extensions optional in frontmatter's layout: blah.liquid
field
#376
Comments
layout: blah.liquid
field
This looks like two separate issues
|
I'll ask the question the other way: why extension is mandatory? |
|
hm fair enough :) Let's add extension into the converter then, but I need to make my though clear on the subject, because Jekyll's theme uses |
With #388, we are no eagerly loading all layouts. One way to improve the error messages is to use an ngram crate to find typos. |
For errors, I created cobalt-org/liquid-rust#184 For migration, I created cobalt-org/cobalt-migrate-jekyll#1 |
At the moment,
.liquid
extension is mandatory.Is there any reason for this?
Again, converting from Jekyll where the layout are often
.html
and no extensions are specified in the front make the converted post failing.Suggestion for the Liquid error message:
Caused by: Layout post can not be read (defined in "posts/2017-05-03-scary-pockets.html"): The system cannot find the file specified. (os error 2)
add quotes around the name of the layout:
Caused by: Layout "post" can not be read (defined in "posts/2017-05-03-scary-pockets.html"): The system cannot find the file specified. (os error 2)
It took me a while to spot the error here ^^'
The text was updated successfully, but these errors were encountered: