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

feat(ERTP): Make recoverySets optional #8406

Closed
wants to merge 2 commits into from

Conversation

erights
Copy link
Member

@erights erights commented Sep 28, 2023

TODO explain

Staged on #8414

@erights erights self-assigned this Sep 28, 2023
@erights erights force-pushed the markm-recovery-sets-optional branch from 38c47ae to 5519cdb Compare September 28, 2023 08:47
Comment on lines +129 to +150
// NOTE: Schema change!
recoverySet: M.opt(M.remotable('recoverySet')),
Copy link
Member Author

Choose a reason for hiding this comment

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

Reviewers,

NOTE: Schema change!

What should we actually do about this?

@erights erights marked this pull request as draft September 28, 2023 08:50
const paymentRecoverySets =
recoverySetOption === 'noRecoverySets'
? undefined
: provideDurableWeakMapStore(issuerBaggage, 'paymentRecoverySets');

Copy link
Member Author

Choose a reason for hiding this comment

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

What if the revived issuer has 'noRecoverySets' but the old state has recovery sets?

@erights erights requested a review from FUDCo September 28, 2023 08:57
Copy link
Contributor

@FUDCo FUDCo left a comment

Choose a reason for hiding this comment

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

This all looks quite plausible to me, but I don't think I'm qualified to comment on whether it's good to go, so I'll leave the approving part to somebody who knows this stuff better.

@erights erights force-pushed the markm-recovery-sets-optional branch from 5519cdb to 2d5c300 Compare September 29, 2023 00:45
@erights erights force-pushed the markm-recovery-sets-optional branch from 2d5c300 to cafb065 Compare October 1, 2023 00:56
@erights erights changed the base branch from master to markm-kill-some-dead-type-decls October 1, 2023 00:58
@erights erights force-pushed the markm-recovery-sets-optional branch 2 times, most recently from 9eb3636 to ead568a Compare October 1, 2023 05:58
@erights erights force-pushed the markm-recovery-sets-optional branch from ead568a to dc6e0f6 Compare October 1, 2023 08:39
Base automatically changed from markm-kill-some-dead-type-decls to master October 2, 2023 00:11
@erights
Copy link
Member Author

erights commented Oct 2, 2023

Closing in favor of #8418

@erights erights closed this Oct 2, 2023
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