-
-
Notifications
You must be signed in to change notification settings - Fork 942
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(music): add album and artist methods #2620
feat(music): add album and artist methods #2620
Conversation
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 normally limit to 1000 entries per file
- Suggest splitting into two PRs, one for adding data for existing methods (since that can be done in a patch release) and one for proposing new methods
- Some of the genres look a bit awkward like "Holiday: Other". Maybe remove ones like that.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #2620 +/- ##
==========================================
- Coverage 99.96% 99.95% -0.01%
==========================================
Files 2973 2975 +2
Lines 212501 214451 +1950
Branches 948 601 -347
==========================================
+ Hits 212422 214358 +1936
- Misses 79 93 +14
|
338b3be
to
1a58eb8
Compare
@matthewmayer thanks for the feedback! I pulled the genre and song name additions out of this PR. Will raise a PR to add and clean up the additional genres. Given the song name set is near 1000 entries I'm discarding all my changes there. I updated the added |
Non ascii names are OK as long as that's how they are normally written in English |
FWIW although we would normally wait for 10 upvotes to approve a change like this this does seem a fairly sensible extension of the current music module so I'd be fine with approving this for next minor or major release. |
Updated to remove albums that could be confusing - the ones that were called out, as well as others I felt could similarly cause some confusion. Updated to case insensitive sort the data as well. Thanks for considering these methods! Would it be possible to add the ask to propose and vote on new modules and methods to the docs and CONTRIBUTING.md? I was unaware this was the general expectation when I got started in the repo 😃 |
Its not really a hard requirement, its more to help triage the issues that are added to the project. So if someone adds an issue saying "it would be cool if we had artist names" we will normally wait until >10 upvotes to see if other people would find it useful. If someone sources suitable data, makes a PR, adds tests etc, then the threshold for inclusion is lower! So I think being too strict about it and documenting in CONTRIBUTING might discourage people from actually contributing code, which we wouldnt want. |
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.
Some small updates to the documentation. Otherwise this looks good to me.
We talked about this PR in today's team meeting. The definitions should follow the method's name unless there is a need for disambiaguation such as with We will rename @matthewmayer What do you think? |
Sure. Shorter is better like city instead of cityName |
@jeremyhofer Could you please apply the requested changes and fix the merge conflicts? |
5e2cee0
a5e9958
This PR introduces two new methods to the
music
module.albumName
andartist
.Data was sourced from various resources from a number of resources online, including:
songName
method was added in feat: add music.songName #996: https://manghammath.com/80s%20Hits/The%20Top%201000%20Songs%20of%20AllTime.pdfThe
@since
version on the methods was set to8.5.0
, as it looks like the8.4.0
tag has been created.