-
Notifications
You must be signed in to change notification settings - Fork 39
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
docs: consolidate proposal shapes #1012
Conversation
@kriskowal thanks for moving Agoric/agoric-sdk#8536 along, but I suspect the ci failure here is due to a regression from that change. Clues?
cc @michaelfig |
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.
👍
The optional **proposalShape** argument can be used to describe the required and allowed components of each proposal. | ||
|
||
### Proposal Shapes | ||
|
||
Proposals that don't match the pattern will be rejected by Zoe without even being sent to the contract. | ||
|
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.
The optional **proposalShape** argument can be used to describe the required and allowed components of each proposal. | |
### Proposal Shapes | |
Proposals that don't match the pattern will be rejected by Zoe without even being sent to the contract. | |
The optional **proposalShape** argument can be used to describe the required and allowed components of each proposal. | |
Proposals that don't match the provided pattern will be rejected by Zoe without even being sent to the contract. | |
### Proposal Shapes | |
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.
I think it was like that before; doesn't that mean people have to read before the heading to get the main point?
fixes #951
closes #739
closes #880
Turns out Proposal Shape was documented already, under
E(zoe).offer(...)
. And the endo reference docs cover Pattern Matchers pretty well.It was also mentioned under zcf.makeInvitation. Since this is the more directly relevant API, I moved the material here and cross-referenced it.
And I copied the
Matchers
interface that gives all the methods ofM
.My editor does markdown lint on save; I hope it's not too distracting that I mixed in work on #945 here. I did put it in separate commits.