Skip to content

Conversation

@salguerooo
Copy link
Contributor

This PR is for adding a setting for showing or hiding the user ratings feature. I was about to open an issue about it but I saw a few others that were already mentioning it so I decided to give it a try.

I think I have covered all the views but please do let me know if I missed something.

These issues are related to this: #1385 #1398

@vercel
Copy link

vercel bot commented Dec 20, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
feishin Ready Ready Preview, Comment Dec 28, 2025 8:57am

@pyxfluff
Copy link
Contributor

pyxfluff commented Dec 20, 2025

I'm confused, is this not what custom CSS is for? Why would you want to remove ratings anyways?

Just seems like bloat for the app and settings menu to me but excuse me if I'm just misinformed

@salguerooo
Copy link
Contributor Author

I come from the Navidrome where you can hide the ratings feature from the UI with an environment variable. I had it turned on initially as it is the default but me and the other person that use the instance really disliked it so we disabled it and never turned back. Now that we're using Feishin as our client we wanted to do the same. I decided to give a shot at implementing it since I saw other issues showing interest in also disabling the ratings feature here.

If this just feels like bloat and doesn't have enough traction to be a feature that's totally fair! I will just go with the custom css solution, but it would be nice to just be able to open the settings and disable it, especially for users that aren't very tech savvy.

@Petersmit27
Copy link

Petersmit27 commented Dec 22, 2025

Chiming in to the discussion, I believe this is a nice feature to have and that Custom CSS should only be recommended as a temporary band-aid fix.

Ultimately, I want to recommend Feishin to non-technical people and telling them to do something with Custom CSS is unacceptable and greatly hinders adoption.
Yes, settings bloat is also a big problem that should be addressed, but I think it's better to add more features and address that than to dismiss user feedback and point them to the Custom CSS setting.

@pyxfluff
Copy link
Contributor

I understand the part about custom CSS but I am yet to see a single reason why there is any need to hide ratings in the first place which is why I simply deemed this as bloat and something that doesn't need to exist. If you don't use ratings you can just ignore it, I don't see why we need to be storing and displaying yet another option and spending the CPU time to decide whether or not to render it

Comment on lines 113 to 119
const columns = useMemo(() => {
if (showRatings) {
return table.columns;
} else {
return table.columns.filter((column) => column.id !== 'userRating');
}
}, [table, showRatings]);
Copy link
Owner

Choose a reason for hiding this comment

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

I would remove this change from all table column instances, as the columns are already configurable to remove the rating column if not desired.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I reverted all the changes on the table columns. I ended up having to change how the cards choose to display the rating stars as well. My initial approach was to remove the onRating completely from all controls but this causes weirdness when the user had the ratings hidden on the settings but choose to display the ratings on any of the tables because the ratings would show up and be interactive on hover but clicking on it would have no effect and I found that interaction to be weird.

@jeffvli jeffvli merged commit df0d4b7 into jeffvli:development Dec 28, 2025
7 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.

4 participants