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

fix: Tighten invitation proposal patterns #6475

Closed
wants to merge 3 commits into from

Conversation

erights
Copy link
Member

@erights erights commented Oct 19, 2022

Staged on #5422 "multiples"

Use tight proposal patterns on production invitations to, among other things, see if the Zoe prohibition on wash invitations is something we should bother preserving. (My assumption is not, but worth doing some of this experiment first.)

@erights erights requested a review from dtribble October 19, 2022 23:14
@erights erights self-assigned this Oct 19, 2022
@erights erights changed the base branch from master to markm-multiples October 19, 2022 23:14
@erights erights requested review from dckc and Chris-Hibbert October 19, 2022 23:15
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 7fe7b4c to 2572b44 Compare October 20, 2022 00:27
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 2572b44 to 61e619c Compare October 20, 2022 04:13
@erights
Copy link
Member Author

erights commented Oct 20, 2022

Reviewers, especially for the occurrences of EmptyProposal, let me know if each one makes sense, and where the corresponding offer call happens. I was not able to find many of those offer calls, and so could not easily tell what proposal pattern is appropriate.

@erights erights force-pushed the markm-invitation-proposal-patterns branch from b7fd28c to 30f1a1f Compare October 20, 2022 19:56
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 30f1a1f to 9165c33 Compare November 5, 2022 03:11
@erights erights removed request for dckc and dtribble November 5, 2022 03:31
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 9165c33 to 5910533 Compare November 9, 2022 05:30
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 5910533 to 5dee4d6 Compare November 9, 2022 22:22
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 5dee4d6 to c2e8a4f Compare November 19, 2022 05:30
@erights erights force-pushed the markm-invitation-proposal-patterns branch from c2e8a4f to 55b5868 Compare December 4, 2022 05:42
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 55b5868 to 2527e69 Compare December 4, 2022 08:42
Comment on lines 292 to 277
M.splitRecord({
give: { In: stableAmountShape },
want: M.or({ Out: anchorAmountShape }, {}),
multiples: 1n,
exit: M.any(),
}),
Copy link
Member Author

Choose a reason for hiding this comment

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

This now represents all the fields of the record, not just a subset. Thus, the M.splitRecord should be removed and the record pattern should be the proposalShape directly.

@erights erights force-pushed the markm-invitation-proposal-patterns branch from 489d586 to 3fd944b Compare December 21, 2022 00:47
@erights erights force-pushed the markm-invitation-proposal-patterns branch 2 times, most recently from 872f99b to d6104d8 Compare December 23, 2022 23:14
@erights erights force-pushed the markm-invitation-proposal-patterns branch from d6104d8 to 6b620ad Compare December 23, 2022 23:23
@erights erights force-pushed the markm-invitation-proposal-patterns branch from 6b620ad to 1a4f7f3 Compare December 23, 2022 23:42
@erights
Copy link
Member Author

erights commented Feb 28, 2023

Closing in favor of #7041

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants