| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Dunno how we missed this one
|
|
...by using the right contributions
|
|
|
|
Not related to other commits in this PR, sorry!!
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This commit only introduces the new behavior which subsequent
commits will depend on. Meanwhile, everything is broken.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also drop this property from Track, Album
|
|
|
|
We probably can just remove the date altogether, but this
change is external only, not logical.
|
|
Used for some truly shenanigans sorting behavior hooked into
by reverse itself, but we won't need this anymore, because
the referencing things will just be the artworks themselves,
already properly dated.
|
|
|
|
Using new find specs {track,album}PrimaryArtwork.
It's still mixedFind, and it still does not support
matching artworks besides the primary one.
|
|
Allow include() to conveniently replicate the same behavior
that it does by default, e.g. if [Thing.findThisThingOnly]
has been expressly disabled.
|
