use YAML parser for meta-data evaluation #259
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The build in meta-data evaluation is going to use a YAML parser. "Normal" meta-data (title, date) should be used and work as before. My main intention is to add support for nested page properties. Allowing structured data could provide great new opportunities. E.g. it can be utilized (by plugins) to provide or alter a configuration on per page basis. For example:
A difference between YAML and Phile is that Phile sanitizes the meta-data keys (lowercase, whitespace to underscore, …). We should keep it that way to provide backwards-compatibility (for now).