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

Handle both 'track' and 'track_name' distinct fields. (Fixes #44) #45

Merged
merged 1 commit into from
May 28, 2020

Conversation

kingosticks
Copy link
Member

'track' is translated to 'track_name' so we remain compatible across Mopidy versions.

@codecov
Copy link

codecov bot commented May 17, 2020

Codecov Report

Merging #45 into master will increase coverage by 0.45%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
+ Coverage   50.39%   50.84%   +0.45%     
==========================================
  Files           9        9              
  Lines         764      765       +1     
==========================================
+ Hits          385      389       +4     
+ Misses        379      376       -3     
Impacted Files Coverage Δ
mopidy_local/library.py 42.42% <100.00%> (+2.72%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 00b8340...5362884. Read the comment docs.

tests/test_library.py Outdated Show resolved Hide resolved
@jodal jodal modified the milestones: v3.1.1, v3.2.0 May 18, 2020
'track' is translated to 'track_name' so we remain compatible across
Mopidy versions.
@kingosticks kingosticks force-pushed the fix/get-distinct-field-track branch from 927cf3b to 5362884 Compare May 28, 2020 23:28
@kingosticks kingosticks merged commit be79bcb into mopidy:master May 28, 2020
@kingosticks kingosticks deleted the fix/get-distinct-field-track branch May 28, 2020 23:47
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.

2 participants