hsmusic-wiki - HSMusic - static wiki software cataloguing collaborative creation

Age	Commit message (Collapse)	Author
2024-12-11	replacer: sigh	(quasar) nebula

2024-12-09	content: generate{Album,Track}CoverArtwork: content warnings(!!)	(quasar) nebula
	oops :+1:
2024-12-09	content: generateCoverArtwork: pass-through warnings slot	(quasar) nebula

2024-12-09	data: Default Track Dimensions	(quasar) nebula

2024-12-05	replacer: fix escaping tildes in content	(quasar) nebula

2024-12-01	language: unflattenLanguageSpec: fix dropping own nodes early	(quasar) nebula
	recovers many strings!
2024-12-01	language: minor style cleanup	(quasar) nebula

2024-12-01	language: unflattenLanguageSpec: simplify {_: ...} tidying	(quasar) nebula
	cleaner solution than "no lonely '_' keys"
2024-12-01	language: unflattenLanguageSpec: fix a problem...	(quasar) nebula
	very descriptive makes one string unflatten that wasn't appearing before (trackPage.socialEmbed.body.withArtists.withCoverArtists)
2024-12-01	css: fix scrollbar-color usage	(quasar) nebula
	Resolves #519.
2024-11-30	content: generateTextWithTooltip: always blank w/ blank text	(quasar) nebula
	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???)
2024-11-30	client: image-overlay: grab color from clicked image	(quasar) nebula

2024-11-30	client: image-overlay: factor out getImageSources	(quasar) nebula

2024-11-30	client: image-overlay: be a client module	(quasar) nebula

2024-11-30	language: unflattenLanguageSpec: no lonely '_' keys	(quasar) nebula
	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.)
2024-11-20	content: generateFlashCoverArtwork: pls <3 pls <3 pls <3 pls <3	(quasar) nebula

2024-11-20	replacer: postprocessComments	(quasar) nebula
	Always say good morning!
2024-11-20	client: scripted-link: ignore while input or textarea focused	(quasar) nebula
	Fixes #551
2024-11-20	content: fix a couple code bugs w/ cover artwork changes	(quasar) nebula
	Oops! All peachy now.
2024-11-19	content, css: generateQuickDescription: use blockquote	(quasar) nebula
	Lets nested blockquote styling kick in.
2024-11-19	content, css: cover artwork reference details, non-unique art line	(quasar) nebula

2024-11-19	data, checks: find.{album,track}WithArtwork	(quasar) nebula

2024-11-19	language: count blankIfZero	(quasar) nebula

2024-11-19	content: generate{Album,Flash,Track}CoverArtwork: mode slot	(quasar) nebula
	Passthrough. This maintains the interface previously used for all cover artworks and therefore obliterates surrounding hacks.
2024-11-19	content: decompose generateCoverArtwork	(quasar) nebula
	No visual/site changes yet. This involves introducing an unfortunate mega-hack in generateStickyHeadingContainer, which sets slots on cover artworks. Very scary. Oooooo Otherwise, all cover artwork code is much more compositional. Pass-through slots (`image`) are removed in generateCoverArtwork and a partially-formed `image` slot is accepted instead.
2024-11-19	html: Template.clone: use "ready" slot values	(quasar) nebula
	This doesn't fix the issue in the context we were trying to fix, but it is semantically correct (where existing behavior is not), which we are not proving with a unit test.
2024-11-19	content: generate{Album,Flash,Track}CoverArtwork: inline alt	(quasar) nebula

2024-11-19	content: generate{Album,Track,}ReferencingArtworksPage	(quasar) nebula

2024-11-19	data: {Album, Track}.referencedByArtworks	(quasar) nebula

2024-11-19	data: withReversList_template: allow mixed types	(quasar) nebula

2024-11-17	content: generate{Album,}ReferencedArtworksPage	(quasar) nebula

2024-11-17	data: fix Album.referencedArtworks being unresolvable	(quasar) nebula

2024-11-17	content: generateTrackReferencedArtworksPage	(quasar) nebula

2024-11-17	content: generateTrackNavLinks	(quasar) nebula

2024-11-17	content: "Illust." -> "Artwork by"	(quasar) nebula

2024-11-17	content, css: generatePageLayout: move subtitle beneath cover	(quasar) nebula

2024-11-17	content, css: generateCoverArtwork: 'primary-artists' mode	(quasar) nebula

2024-11-17	content: misc.albumGrid -> misc.coverGrid	(quasar) nebula

2024-11-17	content: generatePageLayout: showWikiName: 'auto'	(quasar) nebula

2024-11-17	content, css: generatePageLayout: subtitle slot	(quasar) nebula

2024-11-17	data: raiseResolvedReferenceList: remove raiseOutputAbove misref	(quasar) nebula
	Because raiseResolvedReferenceList is the last step in compositions which use it - it always raises the desired conclusion - it doesn't actually need to use raiseOutputAbove.
2024-11-17	content: generate{Artist,Group}InfoPage: alias links	(quasar) nebula

2024-11-17	data, content: closely linked artist annotations	(quasar) nebula
	Basic implementation only here, nothing custom for particular annotations for example.
2024-11-17	data: reverseAnnotatedReferenceList	(quasar) nebula

2024-11-17	data: withResolvedAnnotatedReferenceList: availability checks	(quasar) nebula

2024-11-17	data: withStretchedList	(quasar) nebula

2024-11-17	data: withReverseContributionList: use withPropertyFromList	(quasar) nebula

2024-11-17	data: annotatedReferenceList, reference-list-helpers	(quasar) nebula

2024-11-17	data: withResolvedArtworkReferenceList -> ...Annotated	(quasar) nebula

2024-11-17	data: raiseResolvedReferenceList	(quasar) nebula
	This commit also implements raiseResolvedReferenceList across the compositions which have a notFoundMode input. This causes no semantic changes at all, except that notFoundMode is no longer ignored(!!) in withResolvedContribs.