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

Age	Commit message (Collapse)	Author
7 hours	data: Content: chop almost everything	(quasar) nebula

25 hours	data: various import / unused cleanup	(quasar) nebula

26 hours	data: Artwork: chop withDate	(quasar) nebula
	It wasn't even used to compute the date property...
26 hours	data: constituteFrom, constituteOrContinue	(quasar) nebula

27 hours	data: Artwork: chop withAttachedArtwork & friends	(quasar) nebula

27 hours	data: Artwork: chop withArtTags, withContentWarningArtTags	(quasar) nebula

27 hours	data: Artist: chop artistTotalDuration	(quasar) nebula
	...and depend on resolved reverse reference lists
27 hours	data: ArtTag: chop withAllDescendantArtTags, withAncestorArtTagBaobabTree	(quasar) nebula

27 hours	data: TrackSection: chop with{Start,Continue}CountingFrom	(quasar) nebula

28 hours	data: Album: chop withTracks, withCoverArtDate	(quasar) nebula

2 days	data: Track: chop withPropertyFromAlbum	(quasar) nebula

2 days	data: Track: chop exitWithoutUniqueCoverArt	(quasar) nebula

2 days	data: Track: inline alwaysReferenceByDirectory	(quasar) nebula

2 days	data: Track: chop withTrackNumber	(quasar) nebula
	one """normative""" change: we're checking availability of #index correctly now (in index mode)
2 days	data: Track: chop withDirectorySuffix, withSuffixDirectoryFromAlbum	(quasar) nebula

2 days	data: Track: chop withOtherReleases	(quasar) nebula

2 days	data: Track: chop withAllReleases	(quasar) nebula

2 days	data: Track: chop withMainReleaseTrack	(quasar) nebula
	probably contains normative changes re: dropping notFoundValue behavior in properties which inherit from main release, but has no effect on good wiki data and maybe those compositions resolve the same anyway...
2 days	data: Track: chop withMainRelease	(quasar) nebula

2 days	data: exitWithoutUpdateValue: validate input	(quasar) nebula

2 days	data: Track: chop withCoverArtistContribs	(quasar) nebula

2 days	data: Track: chop withTrackArtDate	(quasar) nebula

2 days	data: Track: chop withDate	(quasar) nebula

2 days	data: Track: chop withHasUniqueCoverArt	(quasar) nebula

2 days	data: spot fixes	(quasar) nebula
	--precache-mode all succeeds
2 days	cacheable-object, data: depend on computed values; initial compat	(quasar) nebula
	reaches live-dev-server serve with no errors and serves homepage at all and apparently correctly no page navigation performed no full build performed aimed for preserving existing logic should be no subsequent changes to this commit (amend)
3 days	composite: nicer input validation error messaging	(quasar) nebula

3 days	data: factor out getOutputName in withPropertyFrom...	(quasar) nebula

3 days	data: ~The Forever Fieldtrip~ (no) more adventures	(quasar) nebula

3 days	data: Artist: fix always having avatar artwork	(quasar) nebula

3 days	data, yaml: save() -> connect(), Thing.wikiData & friends	(quasar) nebula
	HOLY GUACAMOLE
3 days	data, infra: auto-inherit yaml document specs	(quasar) nebula

3 days	data: CacheableObject: fix hasPropertyDescriptor	(quasar) nebula
	can detect stuff from non-null-prototype objects now, but this is for checking the presence of (generally static-queried) descriptors, not listing
3 days	data: Adventure (wip!!!! wip!!!! wip!!!! wip!!!!)	(quasar) nebula

3 days	data, infra: better CacheableObject prototype inheritence	(quasar) nebula
	Basically, properties (as written in source code) are only registered once EVER, instead of "also" on subclasses, which was previously the case - we were literally copying over the descriptors and then re-evaluating as though they were new. That's the goal, but to make it happen, we had to redo how default property values are initialized. Things no longer self- prepare by making a "storage" for all their cached values with null, or defaults, filled in - instead they create a new object which inherits those defaults from their prototype. This object respectively has the prototype of the superclass' prototype's defaults, and so on. A nice effect is that validating defaults against update.validate specs now happens during prototype finalization, instead of every time any instance is instantiated. We also had to do the same kind of inheritence shenanigans with the full propertyDescriptors specs themselves. The real-world performance boost for this is probably more or less zero RIGHT NOW, because Thing subclassing is used crazy sparingly (and there's still work to make it really nice). But if [[Prototype]] chains don't really take memory, then possibly this cleans up a lot of extremely similar objects where every new Thing property multiplies memory usage across all instances of that thing, regardless how few actually set a value. Maybe! Who knows what V8 really optimizes, but maybe!
3 days	data, infra: actually sort subclasses after superclasses	(quasar) nebula
	critically necessary for literally any inheritence shenanigans
3 days	data: link flashes, acts, and sides directly	(quasar) nebula
	same as 67a936adc308a5bec6c969c90d8811fcbce3009b and 4362324b40da9daa54c9c6c3a821b0cccaec71a0 (combined into one and with more save() cleanup)
3 days	can't commit this	(quasar) nebula

3 days	content: image: shush about missing thumbnails	(quasar) nebula

2025-11-04	content: consider language order for tooltip offset	(quasar) nebula

2025-11-04	language: language.orderStringOptions() / language.$order()	(quasar) nebula

2025-11-04	content, css: always control offset-tooltip effect from content	(quasar) nebula

2025-11-04	content: gAIPChunk: albumLink, flashActLink slots -> link	(quasar) nebula

2025-11-04	content: gAIPChunk: items slot -> list	(quasar) nebula

2025-11-03	search: don't count "edits for wiki" for artist groups	(quasar) nebula

2025-11-03	search: fresher artist groups math	(quasar) nebula

2025-11-03	search: first try at artist groups	(quasar) nebula

2025-11-03	cilent, search: access isTrack, isAlbum etc	(quasar) nebula

2025-11-03	client, search: fix bad Object.hasOwn() accesses	(quasar) nebula

2025-11-03	client, search: add additionalNames to interestingFieldCombinations	(quasar) nebula