Allow posts to specify custom templates #8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… (by reverting the paramaterized templateField)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Here's the code I talked about in issue #5. It's based on the current master, so if you decide to go whole hog and merge everything I've submitted, there'll be a conflict or two. If you do want to merge everything, let me know, and I can create a single big pull request that includes everything from my local main development branch.
Anyway, as you can see in the other issue, all this does is allow you to add a YAML header like
template: someTemplate, and it returns the object attemplates.text.someTemplate_html. You can do dotted or slashed paths to templates deeper in the hierarchy too:template: path.to.postortemplate: path/to/postreturn whatever's intemplates.text.path.to.post_html.