Setup Recipe Parser #106
Merged
Setup Recipe Parser #106
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
|
Maybe the fixtures in spec/fixtures/ should just be symlinks to the actual files? That way breakage would be immediately obvious and there'd be less duplication. |
Since our templates inherit from each other we need to understand the content of each of the templates. My long term vision is to create a user friendly version in which all the templates are properly merged together. Then you can just read one of the recipes. It will be automatically added in the proper template. At the same time I still want markdown to be used for all the recipes. That makes it very comfortable to write recipes. At the same time it is also a little easier for everyone to follow the recipes directly in this git repository.
hendricius
force-pushed
the
recipe-parser-setup
branch
from
927d47d
to
947fa38
Compare
|
Thanks. Great idea, done. |
Closed
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.
Since our templates inherit from each other we need to understand the
content of each of the templates. My long term vision is to create a
user friendly version in which all the templates are properly merged
together. Then you can just read one of the recipes. It will be
automatically added in the proper template.
Then you can read all the instructions together in one place.
At the same time I still want markdown to be used for all the recipes.
That makes it very comfortable to write recipes. At the same time it is
also a little easier for everyone to follow the recipes directly in this
git repository.