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

Serverside hidden activities #112

Merged
merged 11 commits into from
May 28, 2024
Merged

Serverside hidden activities #112

merged 11 commits into from
May 28, 2024

Conversation

raikasdev
Copy link
Member

Very epic Rust code. Probably not very good looking and I will be sticking with TS from now.

Adds support for hiding activities for specific projects. This has been implemented client-side with hashes on the VSCode extension but I'd personally prefer to myself see the projects with names. Currently hidden projects can't be distinguished from each other and they will all have a empty string as the project name along with "hidden": true.

Copy link
Member

@lajp lajp left a comment

Choose a reason for hiding this comment

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

Hi, thanks for the PR!
This is definitely a functionality we want.
Here are some minor things I'd like you to address before we can merge this.

migrations/2024-03-12-174132_serverside_hidden/down.sql Outdated Show resolved Hide resolved
migrations/2024-03-12-174132_serverside_hidden/up.sql Outdated Show resolved Hide resolved
src/database/activity.rs Outdated Show resolved Hide resolved
src/database/activity.rs Show resolved Hide resolved
src/api/friends.rs Outdated Show resolved Hide resolved
src/api/friends.rs Outdated Show resolved Hide resolved
src/api/users.rs Outdated Show resolved Hide resolved
@lajp
Copy link
Member

lajp commented Mar 15, 2024

Additionally would it be possible for you or someone else (@Eldemarkki) to implement the funcitonality to the Frontend side so that we can enable it immediately after merging?

@lajp
Copy link
Member

lajp commented Mar 16, 2024

Should we also automatically hide new heartbeats for projects where there exists a hidden project with the same name and from the same user, regardless of what the client says? Or should we just leave the responsibility to the client?

Copy link
Member

@lajp lajp left a comment

Choose a reason for hiding this comment

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

Please fix the tests, otherwise lgtm

Copy link
Member

@DrVilepis DrVilepis left a comment

Choose a reason for hiding this comment

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

kabum

Copy link
Member

@lajp lajp left a comment

Choose a reason for hiding this comment

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

Looks good! Thanks for your contribution and sorry for the slow review.

@lajp lajp merged commit 56fc194 into Testaustime:main May 28, 2024
4 checks passed
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.

3 participants