Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[PM-17168] Sync organization user revoked/restored status immediately via push notification #13101
[PM-17168] Sync organization user revoked/restored status immediately via push notification #13101
Changes from all commits
4ddfc1e
1398c49
cfe0ea4
8acbc16
fffbb5b
f4e4625
4a4e35c
934791c
839eacc
ff7eef9
eb30531
9f6ecfb
1764a8b
3b144ba
57d9548
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 192 in libs/common/src/platform/notifications/internal/default-notifications.service.ts
libs/common/src/platform/notifications/internal/default-notifications.service.ts#L192
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'm actually going to keep the rejection only because I think your server change should be enough for now.
SyncService.fullSync(true)
will automatically callApiService.refreshIdentityToken()
. We are thinking about decoupling that behavior and the change here you have would be right but we are not going to be merging that right now. So please check my assumption here but you should get the desired outcome with only the server PR. I've linked the tickets and mentioned the PR on our decoupling work so that if we go ahead with that we will add theApiService.refreshIdentityToken
call for you.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 didn't know
fullSync
already did this for us, so fwiw I'm OK with that suggestion. Thanks @justindbaurThere 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.
Yes that is true, the server PR changes alone are enough. Thanks for looking into this, @justindbaur!
I'll close this PR.