« get me outta code hell

hsmusic-wiki - HSMusic - static wiki software cataloguing collaborative creation
about summary refs log tree commit diff
path: root/src/data
AgeCommit message (Collapse)Author
45 hourscacheable-object: drop old stuff(quasar) nebula
45 hourscacheable-object: remove 900,000 functions(quasar) nebula
45 hourscacheable-object: tread carefully in {*}PropertyValueError(quasar) nebula
4 daysdata: soupy reverse(quasar) nebula
4 daysdata: misc eslint unused var fixes(quasar) nebula
4 daysyaml, upd8: provide boundReverse(quasar) nebula
4 daysdata: Track: reverse spec fix-ups(quasar) nebula
4 daysdata: Track: stub demo Thing.reverseSpecs(quasar) nebula
4 daysfind, reverse: factor out some common interfaces & stub reverse(quasar) nebula
no bindReverse yet
4 daysdata: general withReverse{*}List logic tidying(quasar) nebula
4 daysdata: withMappedList: 'filter' option(quasar) nebula
4 daysdata: withReverseReferenceList: use withPropertyFromList(quasar) nebula
5 daysdata: use soupyFind everywhere(quasar) nebula
also notes where remaining directly-provided wikiData() props are used
5 daysdata: inputSoupyFind.input()(quasar) nebula
occasionally we use a soupyFind.input() from #composite/wiki-data code, so this exposes a no-dependency frontend for that token
5 daysdata: annotatedReferenceList: gobble + tolerate null data(quasar) nebula
5 daysdata: singleReference: gobble + tolerate null data(quasar) nebula
5 daysdata: Track: stub soupyFind.input demo(quasar) nebula
5 daysdata: referenceList: gobble(quasar) nebula
5 daysdata: inputSoupyFind, gobbleSoupyFind(quasar) nebula
5 daysdata: soupyFind on a couple more objects(quasar) nebula
dodges happenstance dependency issues booting up repl
5 daysdata: Track: stub soupyFind demo(quasar) nebula
5 daysdata, upd8: auto-provide boundFind on 'find' dependency(quasar) nebula
5 daysdata: soupyFind (stub)(quasar) nebula
5 daysdata: withResolvedReferenceList: tolerate null data nicely(quasar) nebula
5 daysdata: inputWikiData: generally accept leaving unspecified(quasar) nebula
5 daysdata: withResolvedReferenceList: use withMappedList(quasar) nebula
6 daysdata: withResolvedContribs: fix bad availability filter(quasar) nebula
Was based on contrib.thing, which is always present. These steps are meant to filter based on the availability of each contribution's artist, since that's a forward reference that may be unavailable in given artistData. Introduced alongside raiseResolvedReferenceList in commit 65ff7444 (i.e. 11/16/2024).
9 daysdata: Album.wallpaperParts(quasar) nebula
12 daysdata: with{Resolved,Reverse}AnnotatedReferenceList: dates(quasar) nebula
12 daysdata: annotatedReferenceList: fix composition annotation(quasar) nebula
2024-12-29data, content: showAlbumArtists: all/differing/none(quasar) nebula
This breaks the build. Oop
2024-12-25data, content: Artist.closelyLinkedGroups: thing -> group(quasar) nebula
2024-12-25data: amorphize reverse annotated reference lists(quasar) nebula
2024-12-25data: withReverseList_template: additionalInputs(quasar) nebula
2024-12-25data, content: Group.closelyLinkedArtists: thing -> artist(quasar) nebula
2024-12-25data: amorphize annotated reference lists(quasar) nebula
2024-12-09data: Default Track Dimensions(quasar) nebula
2024-12-01language: unflattenLanguageSpec: fix dropping own nodes early(quasar) nebula
recovers many strings!
2024-12-01language: minor style cleanup(quasar) nebula
2024-12-01language: unflattenLanguageSpec: simplify {_: ...} tidying(quasar) nebula
cleaner solution than "no lonely '_' keys"
2024-12-01language: unflattenLanguageSpec: fix a problem...(quasar) nebula
very descriptive makes one string unflatten that wasn't appearing before (trackPage.socialEmbed.body.withArtists.withCoverArtists)
2024-11-30language: 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-19data, checks: find.{album,track}WithArtwork(quasar) nebula
2024-11-19language: count blankIfZero(quasar) nebula
2024-11-19data: {Album, Track}.referencedByArtworks(quasar) nebula
2024-11-19data: withReversList_template: allow mixed types(quasar) nebula
2024-11-17data: fix Album.referencedArtworks being unresolvable(quasar) nebula
2024-11-17data: 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-17data, content: closely linked artist annotations(quasar) nebula
Basic implementation only here, nothing custom for particular annotations for example.
2024-11-17data: reverseAnnotatedReferenceList(quasar) nebula