Skip to content
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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

ingydotnet
Copy link
Member

No description provided.

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.
@ingydotnet ingydotnet requested a review from a team as a code owner June 22, 2021 14:45
@ingydotnet ingydotnet changed the title Publish RFCs to https://spec.yaml.io/rfc/ WIP — Publish RFCs to https://spec.yaml.io/rfc/ Jun 22, 2021
@eemeli
Copy link
Member

eemeli commented Jun 22, 2021

I presume that this PR will be rebased after #84 is merged, as it currently appears to contain its changes as well?

@eemeli eemeli removed the request for review from a team August 6, 2021 09:16
@eemeli eemeli marked this pull request as draft August 6, 2021 09:16
@ingydotnet ingydotnet changed the title WIP — Publish RFCs to https://spec.yaml.io/rfc/ Publish RFCs to https://spec.yaml.io/rfc/ Aug 9, 2021
@Thom1729 Thom1729 added the Spec Change Any change to the specification itself label Sep 3, 2021
Copy link

@UnePierre UnePierre left a 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,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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,
  1. Grammar
  2. "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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Spec Change Any change to the specification itself
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants