-
Notifications
You must be signed in to change notification settings - Fork 143
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(notifications): finish migrating gql functionality #3821
Conversation
UncleSamtoshi
commented
Jan 11, 2024
•
edited
Loading
edited
- switch from account settings to user settings
- add notificationSettings to User
- add userEnableNotificationChannel mutation
- add userDisableNotificationCategory mutation
- add userEnableNotificationCategory mutation
@@ -13,50 +13,149 @@ pub struct Query; | |||
#[Object] | |||
impl Query { | |||
#[graphql(entity)] | |||
async fn consumer_account(&self, id: ID) -> Option<ConsumerAccount> { |
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 backwards compatibility won't we need to keep it on consumer_account as well?
Can still return the same
app
.notification_settings_for_user(GaloyUserId::from(self.id.0.clone()))
.await?;
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 types are different now so we can't. I think we will need to keep backwards compatibility by keeping it live on core for a period.
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.
In addition to the mutations on core.
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.
So core will proxy to notifications I for a while I guess.