Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 300
feat: Add new metadata to confirmation controllers#6473
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
Uh oh!
There was an error while loading. Please reload this page.
Changes from all commits
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -147,7 +147,12 @@ export type AddressBookControllerEvents = | ||
| | AddressBookControllerContactDeletedEvent; | ||
| const addressBookControllerMetadata = { | ||
| addressBook: { persist: true, anonymous: false }, | ||
| addressBook: { | ||
| includeInStateLogs: true, | ||
| persist: true, | ||
| anonymous: false, | ||
Member There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Did we plan to rename this to MemberAuthor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes exactly, it will happen as part of the migration to | ||
| usedInUi: true, | ||
| ||
| }, | ||
| }; | ||
| /** | ||
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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.
Minor, very pedantic, but how are deciding the order of these properties if we're defining them in every controller? Alphabetical? Importance?
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 have been putting them in alphabetical order, leaving the order of pre-existing properties alone to minimize churn. I intended to move
anonymousto be alphabetical as part of the rename