-
Notifications
You must be signed in to change notification settings - Fork 5
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 notification response handling #156
Merged
owengretzinger
merged 1 commit into
main
from
01-17-feat_respond_to_notification_functionality
Jan 27, 2025
Merged
feat: implement notification response handling #156
owengretzinger
merged 1 commit into
main
from
01-17-feat_respond_to_notification_functionality
Jan 27, 2025
Conversation
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 was referenced Jan 17, 2025
owengretzinger
changed the title
feat: respond to notification functionality
feat: implement notification response handling
Jan 17, 2025
Graphite Automations"Request reviewers once CI passes" took an action on this PR • (01/17/25)1 reviewer was added to this PR based on Owen Gretzinger's automation. |
owengretzinger
force-pushed
the
01-12-feat_notification_page
branch
from
January 27, 2025 07:47
a0f664b
to
76b6087
Compare
owengretzinger
force-pushed
the
01-17-feat_respond_to_notification_functionality
branch
from
January 27, 2025 07:47
492d5b1
to
a423843
Compare
owengretzinger
force-pushed
the
01-12-feat_notification_page
branch
from
January 27, 2025 07:54
76b6087
to
3aa2f64
Compare
owengretzinger
force-pushed
the
01-17-feat_respond_to_notification_functionality
branch
from
January 27, 2025 07:55
a423843
to
e6b12dd
Compare
owengretzinger
force-pushed
the
01-12-feat_notification_page
branch
2 times, most recently
from
January 27, 2025 08:00
4d8ea59
to
3e713eb
Compare
owengretzinger
force-pushed
the
01-17-feat_respond_to_notification_functionality
branch
from
January 27, 2025 08:00
e6b12dd
to
adb931f
Compare
owengretzinger
changed the base branch from
01-12-feat_notification_page
to
graphite-base/156
January 27, 2025 08:03
owengretzinger
force-pushed
the
graphite-base/156
branch
from
January 27, 2025 08:04
3e713eb
to
9097a7a
Compare
owengretzinger
force-pushed
the
01-17-feat_respond_to_notification_functionality
branch
from
January 27, 2025 08:04
adb931f
to
f05f966
Compare
owengretzinger
force-pushed
the
01-17-feat_respond_to_notification_functionality
branch
from
January 27, 2025 08:04
f05f966
to
b427b7a
Compare
AnkushSarkar10
approved these changes
Jan 27, 2025
Merge activity
|
owengretzinger
deleted the
01-17-feat_respond_to_notification_functionality
branch
January 27, 2025 08:08
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TL;DR
Added notification response functionality allowing users to accept/reject friend requests and habit invites.
Screen.Recording.2025-01-17.at.1.07.37.PM.mov
What changed?
useRespondToNotification
mutation hook to handle notification responsesHow to test?