Recipe timings #39
Open
Recipe timings #39
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
and related schema microformats
Wholly via javascript with no dependencies. This allows for it to be fully compatible with gh_pages
Wholly via javascript with no dependencies. This allows for it to be fully compatible with gh_pages
Allow users to use lowercase in the definitions. This can lead to better readability: preptime: 1h20m
allows for multiple timings per page like when using components
foosel
added a commit
to foosel/food.foosel.net
that referenced
this pull request
Oct 25, 2020
As implemented in clarklab/chowdown#39, extended to include total and active time.
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.
This is a complete rewrite of the previous attempt. This time using pure javascript to process ISO8601 durations. It's not perfect but means this feature will work in
gh_pagesenvironments as well as normal deployments.Recipes will use ISO8601 formats as per previous PR but they will be able to use lowercase which should aid readability:
The
PTbit is needed as mentioned before to separateM(months) fromM(minutes) although we could drop the initialPif that helps.This does support translations and I've included english by default. There is currently no way (that I am aware of) that the app makes a language selection available to the js environment so it can't switch yet but the capability is there when it does.
Here's an exaggerated example:
and a more typical one:
also now works with components: