-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish RFCs to https://spec.yaml.io/rfc/ #85
base: main
Are you sure you want to change the base?
Conversation
Stories are short essays explaining more involved YAML usage and ideas. Docs are developer documentation Added build system support for building them into the site. Also added `make stage` which publishes to: http://<gihub-user-id>-spec.yaml.io for showing live content for pull requests.
I presume that this PR will be rebased after #84 is merged, as it currently appears to contain its changes as well? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please generalize the Implicit Merging (a little).
xxx: 9 | ||
``` | ||
|
||
That is, a merge is takes a sequence of two or more mappings and merges them, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is, a merge is takes a sequence of two or more mappings and merges them, | |
That is, a merge takes a sequence of mappings and merges them, |
- Grammar
- "merging" a single map appear unnecessary, but it might be sensible if the surrounding nodes written as are merges, too, or in generated output. This also expands into the case of an empty list in the
!merge
.
No description provided.