-
Notifications
You must be signed in to change notification settings - Fork 30
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 META delimiter or support 3-hyphen #56
Comments
btw, i'm mostly interested in this because I have heaps of files formatted like:
that i'd like to be able to drop into Frank |
Wouldn't be opposed to a.) at all, and it shouldn't conflict with anything. The yaml gets pulled out before anything else sees it. |
This type of delimiter, as far as I understand, is also necessary to be able to use |
Where are you using the data that you are reading from the dynamic file? The idea of the yaml header was that all of the keys would be available in your layout and templates automatically. That being said, the only reason I haven't already switch the delimiter is because i'm wanting to rewrite the entire project, just haven't found the time yet. |
I was looking to read the YAML from a helper method which gathers information about some of the files in a given folder to list the files along with some of their YAML data for an "index" page type functionality. |
Ah, yeah. I'd suggest reading the file, splitting at the delimiter and just parsing the YAML bit for now, or take a stab at forking and changing the delimiter yourself to see if it gets you what you want. |
Parsing the YAML by using |
Leaving this open because it is on the list for the next release. |
It is pretty common to use triple hyphens or equals to delimit a YAML header. For example blogofile, Jekyll, ymlfront plugin for ikiwiki, lots of others. Triple hyphen is also the standard YAML document separator.
It would be nice if:
a. Frank supported this delimiter out of box. Are there known conflicts with supported template languages for this delimiter?
b. The delimiter regex was customizable in setup.rb.
If a. then edrex doesn't care about b.
I can make a patch for a or b.
The text was updated successfully, but these errors were encountered: