smartplaylist: Respect sort terms in queries

[djl]

It would be nice to be able sort items in smart playlists, like so:

smartplaylist:
  relative_to: ~/music
  playlist_dir: ~/.mpd/playlists
  playlists:
    - name: '2014.m3u'
      query: 'year:2014 added+'
    - name: 'imported-%time{$added,%Y-%m}.m3u'
      query: "added:: path+"

I'm unfamiliar with the code but it looks like the smartplaylist plugin discards the query sort field when building playlists. Would it be possible to keep the custom sort?

[sampsyo]

Indeed; it is unfortunate that the plugin discards the sort—I 100% agree that this deserves fixing.

[PierreRust]

For a single query it should be relatively easy to preserve the sort , I think we simply need to add it to the call lib.albums(query): and lib.items(query); a few lines bellow.

But when using a list of query, which is supported by the plugin, which sort specification should we use ?
For example :

name: 'BeatlesUniverse.m3u'
query: ['artist:beatles added+', 'genre:"beatles cover year+"']

[djl]

Intuitively, I would assume that would produce a list made from joining the results of two sorted queries (query1.extend(query2)).

[djl]

Here's my attempt at a solution plus the config I tested with:

smartplaylist:
  playlists:
    - name: 'year-2014.m3u'
      query: ['year:2014 path-', 'year:2012 added+']
    - name: 'imported-%time{$added,%Y-%m}.m3u'
      query: "added:: path+"

The resulting playlists contain the items I expected when compared with a handful of manually built playlists.

As I said I'm not familiar with the code base so this could be the wrong way to do it but it seems to work :)

[sampsyo]

This looks great, @djl! Could you please open a pull request?