-
Notifications
You must be signed in to change notification settings - Fork 774
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: notification #148
base: main
Are you sure you want to change the base?
feat: notification #148
Conversation
@Aashish-Upadhyay-101 is attempting to deploy a commit to the mftsio Team on Vercel. A member of the Team first needs to authorize it. |
…into feat-webhook
…ay-101/papermark into feat-notification
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.
Looks really good @Aashish-Upadhyay-101 !
I think this feature will enable a lot of great use cases.
I made in-line notes.
Another thing that I noticed, you currently scoped Notification
and Webhook
by User
. I think we need to scope it by Team
instead.
I don't think you need to change the API routes, you just need to request the current teamId from the user inside the API functions.
Let me know if you have any questions about it
@mfts webhook and notification now have 3 events i.e. |
@mfts ready for review, for "document_viewed" event !