-
-
Notifications
You must be signed in to change notification settings - Fork 775
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
Build Front-End of Notifications for Gitcoin #2404
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.6 ETH (136.33 USD @ $227.22/ETH) attached to it as part of the Gitcoin fund__.__
|
Sketch file here: |
Thanks @willsputra! @Anish-Agnihotri to answer your question, this is a front-end ticket....please stub out dummy data as a placeholder to where we'd link up the BE dynamic template vars. @usmanmuhd thanks for your interest! I have another ticket for you if you're interested! |
@PixelantDesign Sure! |
This comment has been minimized.
This comment has been minimized.
3 similar comments
@Anish-Agnihotri Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@Anish-Agnihotri Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@Anish-Agnihotri Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
Seems like @gitcoinbot is really set on nagging me about this, haha. I'll be pushing out a WIP PR this weekend. Been down with a fever for the past two days and am in bed, so programming has come down to snail speed. I'll get this knocked out though :). |
How's it going @Anish-Agnihotri ? 🙂 |
This comment has been minimized.
This comment has been minimized.
1 similar comment
@Anish-Agnihotri Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
Hey @Anish-Agnihotri , are you still working on this? |
@willsputra Hey, apologies for going completely MIA on this issue. Certainly not good at all. It's 11/01. Give me till 11/03 and I'll get this knocked out and pushed on it's way. Thanks again. |
Status update: I've gotten the modal working and everything is up and live. Figuring out notification integration and how to persistently populate the status bar dropout with content. |
@Anish-Agnihotri thanks for the update! let us know if you have any questions :) |
i'm very excited about this... @Anish-Agnihotri let us know what you need from us! |
For sure :). My apologies for continued delay due to Diwali today. I'm attempting to pull notifications now and seeing how it is done in the back-end for the New Bounty emails for some reference. Looking to get a WIP PR, and this knocked out asap. |
@Anish-Agnihotri how goez it |
This comment has been minimized.
This comment has been minimized.
1 similar comment
@Anish-Agnihotri Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
This comment has been minimized.
This comment has been minimized.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 3 years, 1 month ago. 1) usmanmuhd has been approved to start work. I will create the backend as discussed with @octavioamu Learn more on the Gitcoin Issue Details page. |
@octavioamu @usmanmuhd notifications examples based on the list |
@usmanmuhd looking forward to seeing a pr! |
Closing this out as we've got the base PR in |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 0.6 ETH (74.54 USD @ $124.24/ETH) has been submitted by: @PixelantDesign please take a look at the submitted work:
|
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 0.6 ETH (71.69 USD @ $119.48/ETH) (plus a crowdfund of 0.4 ETH worth 47.7918933 USD) attached to this issue has been approved & issued to @usmanmuhd. Thanks to @Anish-Agnihotri, @vs77bb for their crowdfunded contributions to this bounty.
|
User Story
Why Is this Needed
Summary: Currently we email community members on things they need to act upon but there isn't a central place on Gitcoin that users can go to to view all notifications and take action.
Description
This task is to build the front-end of the notification system.
Definition of Done
Notifications will be generated each time a user needs to take action upon something (approve worker, disapprove worker, accept worker, receive tip, etc)
Here are the potential notifications we are hoping for:
For Funders
For Hunters
Additional Information
Please review with a core team member @PixelantDesign @willsputra @owocki
Technical Approach
This should just be a new app named 'inbox' with one model Notification that has the following fields
pk
created_on
to_user_id
from_user_id
CTA_URL
CTA_Text
message_html
is_read (bool)
we will likely also want an easy helper function that can be used to create new Notifications
The text was updated successfully, but these errors were encountered: