Update Jekyll and Hugo presets to support all configured post types #685
Conversation
This file contains 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
paulrobertlloyd
added
enhancement
paulrobertlloyd
force-pushed
the
feat/decoupled-preset-post-types
branch
2 times, most recently
from
a6fa7d8 to
4efc6ab
Compare
paulrobertlloyd
force-pushed
the
feat/decoupled-preset-post-types
branch
from
4efc6ab to
380679e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Following on from #680, which removed the limitation around which properties could be output in a template, this PR updates the Jekyll and Hugo presets so that they support writing posts and files to a content store for any configured post type. It also reorganises plugins so split out
getPostTypeandgetPostTemplatefunctions into separate files and tests.