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(notifications): finish migrating gql functionality #3821

Merged
merged 5 commits into from
Jan 12, 2024

Conversation

UncleSamtoshi
Copy link
Contributor

@UncleSamtoshi UncleSamtoshi commented Jan 11, 2024

  • switch from account settings to user settings
  • add notificationSettings to User
  • add userEnableNotificationChannel mutation
  • add userDisableNotificationCategory mutation
  • add userEnableNotificationCategory mutation

bodymindarts
bodymindarts previously approved these changes Jan 12, 2024
@@ -13,50 +13,149 @@ pub struct Query;
#[Object]
impl Query {
#[graphql(entity)]
async fn consumer_account(&self, id: ID) -> Option<ConsumerAccount> {
Copy link
Member

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?;

Copy link
Contributor Author

@UncleSamtoshi UncleSamtoshi Jan 12, 2024

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.

Copy link
Contributor Author

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.

Copy link
Member

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.

@UncleSamtoshi UncleSamtoshi merged commit 93a01a0 into main Jan 12, 2024
15 checks passed
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.

3 participants