| Age | Commit message (Collapse) | Author |
|---|
|
Utilizes availability checks instead of manual null comparisons and
empty() calls, extracts track lists using withPropertyFromList,
operates on index instead of unique album object where possible
(including found / not found check).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This seems to be a bit more reliable, although it'll probably take
a little more memory while serving larger files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also warn with some details when getMatchableNames returns values
besides strings.
This was getting caught on links to listings, which don't have
(data-represented) names.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Poor (read: largely outdated) code documentation is worse than
no code documentation.
The various infrastructural systems specially designed for hsmusic
should get more dedicated reference material, but that can't well
be written before the systems are tested and used for longer.
The compositional data processing style has just about settled,
but it's still very young (compared to, say, the overarching data-
to-page flow, content functions, or the HTML and content template
systems).
|
