-
Notifications
You must be signed in to change notification settings - Fork 557
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: Implement interface persistence #2856
Open
hmalik88
wants to merge
31
commits into
main
Choose a base branch
from
hm/implement-interface-persistence
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 9 commits
Commits
Show all changes
31 commits
Select commit
Hold shift + click to select a range
43ce993
implement interface persistence
hmalik88 d598379
Merge branch 'main' into hm/implement-interface-persistence
hmalik88 7335c30
update coverage
hmalik88 0a19daf
test fixes
hmalik88 5c4f5b8
update coverage
hmalik88 bf86a94
update params
hmalik88 5fd08ae
update more types
hmalik88 4c84900
fix tests
hmalik88 6f40593
fix tests
hmalik88 e5b4551
address PR comments
hmalik88 1afed94
Merge branch 'main' into hm/implement-interface-persistence
hmalik88 7a516fb
Merge branch 'main' into hm/implement-interface-persistence
hmalik88 2ab88f0
update coverage
hmalik88 e005581
add logic to cleanup notification interfaces
hmalik88 5cbc1a7
update tests
hmalik88 686b1fa
update yarn.lock
hmalik88 3d89f80
add ts expect error
hmalik88 305980c
fix coverage and add missing event
hmalik88 58fce06
add missing event
hmalik88 4dc542d
update coverage
hmalik88 c988b19
fix more tests
hmalik88 89d529c
fix coverage again
hmalik88 47545fc
Merge branch 'main' into hm/implement-interface-persistence
hmalik88 a90208a
use weakmap to maintain function reference
hmalik88 291af42
Merge branch 'main' into hm/implement-interface-persistence
hmalik88 d361570
update coverage
hmalik88 e05f6f0
rebuild
hmalik88 0c5bd6d
address PR comments
hmalik88 c599507
update coverage
hmalik88 c6bfb69
update coverage again
hmalik88 c130124
update types
hmalik88 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
{ | ||
"branches": 92.73, | ||
"functions": 96.65, | ||
"lines": 97.99, | ||
"statements": 97.69 | ||
"branches": 92.65, | ||
"functions": 96.7, | ||
"lines": 97.95, | ||
"statements": 97.65 | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Wondering if we should have any limits on this? How long do we persist Snap notifications for?
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 this is mainly to cover the edge case where the interface is lost for the detailed view notification across sessions. I realize it would persist an unread notification's interface indefinitely if the user never reads it, but that's an extreme edge case. I've started conversation with the notification team about exposing some settings to the user to control the lifecycle of notifications.