-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
Feature/313 - Add album details view #346
Conversation
Hello @Yooooomi could you have a look please :) |
cfr. #348 (comment) I think that all requests using For the rest of this PR, the result seems pretty good! However I think there are some ESLint errors that need to be fixed before merging |
<Link to={`/album/${album.id}`} className={s.root}> | ||
{album.name} | ||
</Link> |
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.
Isn't that what InlineAlbum does?
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.
We are in InlineAlbum, and it wasn't 🤔 Maybe I didn't got your comment
onArtistClick={goToArtist} | ||
onTrackClick={goToTrack} | ||
onAlbumClick={goToAlbum} |
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.
Nitpick, but would be nicer to have onTrackClick, onAlbumClick, onArtistClick in this order, from small container to bigger
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.
Done, but anyway we should get rid of this and find a cleaner way to do it. It doesn't seem very maintainable.
BTW the order (artist > track > album) is following the actual order in the search result popup.
onArtistClick, | ||
onTrackClick, | ||
onAlbumClick, |
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.
same here
return ( | ||
<FullscreenCentered> | ||
<Text element="h3"> | ||
You never listened to this song, might be someone else registered |
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.
You never listened to this Album
{ $lookup: { | ||
from: 'tracks', | ||
localField: 'id', | ||
foreignField: 'id', | ||
as: 'track' | ||
}}, |
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.
yes indeed is the same pattern as #348
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.
I'll let @quentinguidee do the edit in his MR after me merged this one has mentioned in this comment : #346 (comment)
I see you have the total time you listened to a specific album. Would be nice, for consistency, to have the same stat in the artist and track stat page (the times listened and total duration underneath). Nice design btw I like it :) |
Hello again. I realised I forgot to thank you for the job you've done. Thanks a lot man it means a lot that people get into the project to add new features! EDIT: just changed the target branch for this PR, I am sorry seeing all the merge conflicts. |
I will do it in another MR if you don't mind, as it has nothing to do with the topic of this one :) |
I kinda don't agree as consistency should be done as we develop new features so we don't pile up inconsistency debt. But don't worry I'll take care of this before releasing. |
I mean, I did it already but in another branch. So don't worry, I will just include it in this PR |
Thanks 🙏 |
I got them when starting the dev.sh containers yesterday. However that was before the recent changes in release/1.8.0, so maybe they are not present anymore. Also I think there are also issues with eslint in release/1.8.0 so you can probably ignore them for now |
Yeah eslint in 1.8.0 is a mess, I've set up a stricter linting than before so don't bother about it! Thanks a lot guys for the work. I'll try to merge them by tomorrow evening or so. You guys rock |
I'm still trying to merge the branch into my branch. What a nightmare 🤯 |
onArtistClick, | ||
export default function SideSearch({ | ||
onTrackClick, | ||
onArtistClick, | ||
onAlbumClick, | ||
inputClassname, | ||
}: ArtistSearchProps) { | ||
}: SideSearchProps) { |
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.
Typo, Sider
I can take care of it if you want. Basically everything in client/ is now in apps/client |
Should be good but if you can check if I didn't break anything you made. Could be nice thanks 🙏 |
Since the merge, I'm getting a |
It seems that you did not run migrations. Do you run the project using docker and dev.sh? |
I am also having issues with migrations. I'll keep in touch. |
I fixed migrations :) |
I'm getting a blank page for album page, I'm trying to fix. |
Everything works! Nice job, thanks for everything :) |
Changelog
Doing the code to handle this feature request : #313
Backend Changes ⚙️
Added a new endpoint to retrieve album information:
Introduced a new endpoint to retrieve album rankings:
Updated the endpoint for retrieving artist statistics:
Frontend Changes 💻
Implemented a new album detail page:
Added links to album pages wherever an album is mentioned across all pages.
Added a most listened album panel to the artist page.