| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
This breaks the build. Oop
|
|
If the CSS works, the CSS works. (Groan)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also some descriptions, because the dynamic behavior of this
component is... pretty dynamic!
|
|
Just cleanup! class slots are so oldschool.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
oops :+1:
|
|
|
|
|
|
|
|
recovers many strings!
|
|
|
|
cleaner solution than "no lonely '_' keys"
|
|
very descriptive
makes one string unflatten that wasn't appearing before
(trackPage.socialEmbed.body.withArtists.withCoverArtists)
|
|
Resolves #519.
|
|
Resolves #528. No particular content changes in practice,
or at least none for commentary entries without dates.
(Maybe commentary entries which have date-retrieved
but not basic date???)
|
|
|
|
|
|
|
|
This might be a crude implementation, but keeps language results
from including {_: 'some string...'} objects that don't have any
other keys, even when preventing so causes a mismatch with the
reference spec/layout. (Of course, the "mismatch" is only
presentationally and not semantically, and we already make other
presentational differences because we output JSON and not YAML
in this function.)
|
|
|
|
Always say good morning!
|
|
Fixes #551
|
|
Oops! All peachy now.
|
