-
Notifications
You must be signed in to change notification settings - Fork 4
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
Vinegar RFC #42
Vinegar RFC #42
Conversation
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.
Broadly looks good, apart from a few structural comments. There are a few issues though:
- this doesn't follow the issue template, and essentially only addresses the
Detailed design
section thereof; - this doesn't have an RFC number (although I can quickly allocate one when this is ready to merge).
@mrmr1993 Thank you for the feedback.
|
05581a8
to
4790775
Compare
65676a3
to
4d4df39
Compare
@@ -23,7 +23,7 @@ In general: | |||
|
|||
* Be specific. This document is meant to share intent to your colleagues. Share what you believe you will actually do. | |||
* Be decisive. No maybes. Any uncertainty can be captured in the unresolved questions section at the end. | |||
* Provide design contex so that we can align on and commit to a technical design. |
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.
For the reviewers: changes in 001-template.md
are orthogonal, but very cosmetic, and it would be very hard to merge a separate PR because it needs a lot of approvals. So I want to add it here. It's a separate commit, so can be reverted individually if needed.
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.
Detail LGTM. See comments for spelling nits, and an answer to the unresolved question.
Consider inlining the answer and removing the unresolved question before merging, and please choose the next sequential RFC number as you merge.
@mrmr1993 all addressed, assigned number 12 (next sequential after zkapps), merging. |
This introduces the RFC describing vinegar, the compatibility layer for pickles.
PRs merging documentation for pickles created when sketching this RFC: