| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 11 days | data, thumbs: Flash.coverArtwork | (quasar) nebula | |
| 11 days | data: withResolvedAnnotatedReferenceList: drop date input | (quasar) nebula | |
| 11 days | data: Artwork.dimensions | (quasar) nebula | |
| 11 days | data: annotatedReferenceList, etc: default date to null | (quasar) nebula | |
| We probably can just remove the date altogether, but this change is external only, not logical. | |||
| 11 days | data: withConstitutedArtwork: don't pass find through | (quasar) nebula | |
| The whole point of constituting artworks in advance is so that they exist with a stable identity having been collected into artworkData during save() from various data loading steps. (The new data check reportOrphanedArtworks confirms this at runtime.) We already included artworkData in linkWIkiDataSpec for exactly this purpose, so just drop the 'find' dependency and transfer here. As a result, constitutibleArtworkList has no dependencies of its own, and dependencies on coverArtworks, trackArtworks, etc come only from earlier steps, i.e. deciding whether or not to constitute an artwork in the first place. | |||
| 11 days | data: constitutibleArtworkList.fromYAMLFieldSpec | (quasar) nebula | |
| Also file extension property passing. | |||
| 11 days | data: Artwork, constitutibleArtwork, etc | (quasar) nebula | |
| Not used in content yet. | |||
| 11 days | data, content: always fallback coverArtDate to date | (quasar) nebula | |
| 2025-01-11 | data: soupy reverse | (quasar) nebula | |
| 2025-01-11 | data: misc eslint unused var fixes | (quasar) nebula | |
| 2025-01-11 | data: general withReverse{*}List logic tidying | (quasar) nebula | |
| 2025-01-11 | data: withReverseReferenceList: use withPropertyFromList | (quasar) nebula | |
| 2025-01-11 | data: use soupyFind everywhere | (quasar) nebula | |
| also notes where remaining directly-provided wikiData() props are used | |||
| 2025-01-11 | data: 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 | |||
| 2025-01-10 | data: annotatedReferenceList: gobble + tolerate null data | (quasar) nebula | |
| 2025-01-10 | data: singleReference: gobble + tolerate null data | (quasar) nebula | |
| 2025-01-10 | data: referenceList: gobble | (quasar) nebula | |
| 2025-01-10 | data: inputSoupyFind, gobbleSoupyFind | (quasar) nebula | |
| 2025-01-10 | data: withResolvedReferenceList: tolerate null data nicely | (quasar) nebula | |
| 2025-01-10 | data: inputWikiData: generally accept leaving unspecified | (quasar) nebula | |
| 2025-01-10 | data: withResolvedReferenceList: use withMappedList | (quasar) nebula | |
| 2025-01-09 | data: 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). | |||
| 2025-01-03 | data: with{Resolved,Reverse}AnnotatedReferenceList: dates | (quasar) nebula | |
| 2024-12-25 | data: amorphize reverse annotated reference lists | (quasar) nebula | |
| 2024-12-25 | data: withReverseList_template: additionalInputs | (quasar) nebula | |
| 2024-12-25 | data: amorphize annotated reference lists | (quasar) nebula | |
| 2024-11-19 | data: withReversList_template: allow mixed types | (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 | data: reverseAnnotatedReferenceList | (quasar) nebula | |
| 2024-11-17 | data: withResolvedAnnotatedReferenceList: availability checks | (quasar) nebula | |
| 2024-11-17 | data: withReverseContributionList: use withPropertyFromList | (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. | |||
| 2024-11-17 | data: factor out inputNotFoundMode | (quasar) nebula | |
| 2024-11-15 | data: Referenced Artworks | (quasar) nebula | |
| 2024-11-14 | data: Track.suffixDirectory, Album.directorySuffix | (quasar) nebula | |
| 2024-11-14 | data: withDirectoryFromName: move to helpers | (quasar) nebula | |
| Also remove the more-composable default behavior of using the current thing's name, because this is no longer meant to be composed generally. | |||
| 2024-11-14 | data: annotated artwork references | (quasar) nebula | |
| Not used on-site, but this is all coded internally. | |||
| 2024-11-02 | data: series list showAlbumArtists | (quasar) nebula | |
| 2024-11-02 | data: seriesList: expose group | (quasar) nebula | |
| 2024-11-02 | data: withResolvedSeriesList: empty if null | (quasar) nebula | |
| 2024-11-02 | data: Group.serieses | (quasar) nebula | |
| 2024-09-04 | data: reverseSingleReferenceList | (quasar) nebula | |
| 2024-09-04 | data: withReverseList_template | (quasar) nebula | |
| 2024-06-26 | data: withReverse{Contribution,Reference}List: sort by date | (quasar) nebula | |
| 2024-06-23 | data: withParsedCommentaryEntries: dateKind, secondDate | (quasar) nebula | |
| 2024-06-21 | data: withParsedCommentaryEntries: auto-fill archive capture dates | (quasar) nebula | |
| 2024-06-21 | data: withParsedCommentaryEntries: accessDate, accessKind | (quasar) nebula | |
| 2024-06-18 | data: Contribution.artistProperty | (quasar) nebula | |
| 2024-06-18 | data: withReverse{Reference,Contribution}List: factor commonality | (quasar) nebula | |
| This doesn't actually move the common behavior into e.g. devoted component compositions - these two still mirror each other - but it *does* isolate the differing behavior in terms of dependencies that are computed uniquely but surrounded by identical compositional steps. This generally seems like a good fit for compositional subroutines, but those aren't official yet. Meanwhile, this is still factored much better than the previous implementation, and hopefully easier to follow as well! | |||
 |
index : hsmusic-wiki | |
| HSMusic - static wiki software cataloguing collaborative creation | Quasar Nebula |
| about summary refs log tree commit diff |