In meta_yaml recipes section, dict_object
s should be a list element
#140
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 is a stepping stone between #137 and #139.
It just says that dict_objects, if given, should look like this:
✅
and not like this:
❌
Note the
-
in the former (correct) example.This is actually bringing us back into alignment with the original spec, which I (mistakenly) revised in:
The motivation here is that, just because we have
dict_object
s as part of the recipe, we should not be limited to having a single dictionary, or possibly from mixing regular recipe declarations with dict_objects (if we want).Note that the existence of the schema added in #137 makes it easy to reason about what's allowed and what's not allowed! (That information is not longer obscured in dense procedural code, as it was previously.) 😄