You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When lastgenre.prefer_specific is enabled but lastgenre.canonical is not beet lastgenre will fail to apply any genres. This could be better documented.
Error message
It would be nice if there would be a error message when prefer_specific is enabled but canonical is not.
The current behaviour:
$ # with prefer_specific but without canonical:
$ beet lastgenre LITE Cubic
lastgenre: genre for album LITE - Cubic (None):
$ # compare: with canonical:
$ beet lastgenre LITE Cubic
lastgenre: genre for album LITE - Cubic (artist): Post-Rock
Suggested behaviour:
$ # with prefer_specific but without canonical:
$ beet lastgenre LITE Cubic
lastgenre: ERROR: `lastgenre.prefer_specific` is enabled but `lastgenre.canonical` is not. Please either disable `prefer_specific` or enable`canonical`!
Documentation
Currently the documentation only hints at this requirement. One could possibly make this clearer.
Alternatives
Alternatively the default canonicalisation tree could just be loaded. Care must be taken to only use it for sorting, not canonicalisation.
The text was updated successfully, but these errors were encountered:
Problem
When
lastgenre.prefer_specific
is enabled butlastgenre.canonical
is notbeet lastgenre
will fail to apply any genres. This could be better documented.Error message
It would be nice if there would be a error message when
prefer_specific
is enabled butcanonical
is not.The current behaviour:
Suggested behaviour:
Documentation
Currently the documentation only hints at this requirement. One could possibly make this clearer.
Alternatives
Alternatively the default canonicalisation tree could just be loaded. Care must be taken to only use it for sorting, not canonicalisation.
The text was updated successfully, but these errors were encountered: