Skip to content
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: add notifications UI #1

Open
wants to merge 107 commits into
base: development
Choose a base branch
from
Open

feat: add notifications UI #1

wants to merge 107 commits into from

Conversation

zugdev
Copy link
Collaborator

@zugdev zugdev commented Dec 7, 2024

@zugdev zugdev requested a review from 0x4007 as a code owner December 7, 2024 17:40
@zugdev zugdev marked this pull request as draft December 7, 2024 17:43
@zugdev
Copy link
Collaborator Author

zugdev commented Dec 7, 2024

@rndquu could you please increase the auth token expiry date in supabase?

@0x4007
Copy link
Member

0x4007 commented Dec 8, 2024

@zugdev pull tag here

@0x4007
Copy link
Member

0x4007 commented Jan 21, 2025

@zugdev @gentlementlegen @rndquu @whilefoo can you guys prioritize finishing this

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the commented code

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it would be more proper to add the data into separate JSON files and mark is as generated through linguist, because the code can barely be viewed (is it actually code or just data)?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is data 0x4007 sent to me, it was super helpful cause my inbox was empty. I though I'd leave it, cause it might help development in the future.

src/home/home.ts Outdated
console.log(err);
});
}
// if ("serviceWorker" in navigator) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you move the PWA capabilities or forgot to un-comment it?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

forgot, thanks for the catch

@gentlementlegen
Copy link
Member

gentlementlegen commented Jan 22, 2025

It seems that the yarn.lock is not updated with the corresponding package.json.
Also, between 861px and 1005px, no search bar is displayed.

@zugdev
Copy link
Collaborator Author

zugdev commented Jan 22, 2025

fixed all, I suppose. @gentlementlegen, I've had problems with yarn.lock in the past, if it still doesnt look right, would you mind going in and generating for me?

@gentlementlegen
Copy link
Member

gentlementlegen commented Jan 23, 2025

@zugdev lock file look fine now, cypress test ran (but some tests failed). Lemme me check again the code and the responsive and I'll approve this.


Responsive and code are resolved. How do I get notifications to appear? It was always empty when I tested it.

@zugdev
Copy link
Collaborator Author

zugdev commented Jan 23, 2025

@zugdev lock file look fine now, cypress test ran (but some tests failed). Lemme me check again the code and the responsive and I'll approve this.

Responsive and code are resolved. How do I get notifications to appear? It was always empty when I tested it.

There is some filtering done. It has to be an issue in a valid Ubiquity org, it's gotta have a price tag and an assignee. The notification reason has to be something involving a comment which can't be from a bot. Notice there is a toggle for bot notifications.

image image

@gentlementlegen
Copy link
Member

No luck with show / hide bot button either, but since it seems to work for you and @0x4007 I trust you.

@zugdev
Copy link
Collaborator Author

zugdev commented Jan 23, 2025

No luck with show / hide bot button either, but since it seems to work for you and @0x4007 I trust you.

If you open your console it should tell you why your notifs have been filtered:

notif 1 filtered because not in org
notif 2 filtered because no price label
...

hopefully that helps

@gentlementlegen
Copy link
Member

Yes thank you, it seems that the only notifications I have come from my dummy organization, and I have none in ubq repos. What are the notifications from exactly?

@0x4007
Copy link
Member

0x4007 commented Jan 23, 2025

Yes thank you, it seems that the only notifications I have come from my dummy organization, and I have none in ubq repos. What are the notifications from exactly?

GitHub has an API endpoint to load your notifications.

@zugdev
Copy link
Collaborator Author

zugdev commented Jan 23, 2025

Yeah this project is a ubiquity specialized GitHub inbox basically. We filter a lot and order by priorities, the goal is to ensure proper prioritization.

@0x4007
Copy link
Member

0x4007 commented Jan 23, 2025

Yeah this project is a ubiquity specialized GitHub inbox basically. We filter a lot and order by priorities, the goal is to ensure proper prioritization.

These rely on our special labels, specifically the priority labels.

@whilefoo
Copy link

image
image
I get different notifications than on Github, is that expected?

@gentlementlegen
Copy link
Member

Not sure how GitHub notifications work but here is what I have as well
image

But then I saw the logs
image

So it seems to make sense. Notifications are only the unread ones (the ones highlighted in your GitHub notifications).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Custom Notifications Viewer
5 participants