-
Notifications
You must be signed in to change notification settings - Fork 686
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
Added missing distinct fields so they match search #1900
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1900 +/- ##
===========================================
+ Coverage 76.91% 76.93% +0.01%
===========================================
Files 55 55
Lines 4669 4673 +4
===========================================
+ Hits 3591 3595 +4
Misses 1078 1078
Continue to review full report at Codecov.
|
A problem I have introduced here is that |
Hmm, any backend with a Fortunately, very few backends support
I can submit PRs for these. |
This has turned into a bit of a mess. |
Remaining issues are:
|
fc9feca
to
c026cfb
Compare
With the exception of 'any' as it doesn't make sense here. Also added some basic get_distinct tests.
…bility. Warn that 'track' is deprecated. Backends should handle both in the short-term.
Co-Authored-By: Stein Magnus Jodal <stein.magnus@jodal.no>
Frontends should use 'track_name'' instead.
2150998
to
f13cfcb
Compare
9e4e5f9
to
7656eff
Compare
OK, I think this version is clearer (less magic) and fixed CI failures. |
And some better tests
7656eff
to
76b4cd3
Compare
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 just wanted to reply to comments but seems I've done a review!
Also added the musicbrainz_* and disc_no fields.
This still needs a changelog entry, I guess it's a feature release?. Technically any frontend that supports distinct (!) and was trying to use field='track', will find that no longer works. So maybe this is a breaking change.. oops.