Repository navigation
v0.9.14
Release v0.9.14
📦 NPM packages
🐳 Docker image
docker pull ms2data/malloy-publisher:0.9.14
docker pull ms2data/malloy-publisher:latest
ℹ️ Details
- Release branch:
release/v0.9.14 - Triggered by: @kylenesbit
ReportEditor can run its queries at a pinned version while the document stays unversioned
ReportEditor takes a new optional queryVersionId. The ?versionId= on resourceUri decided two things at once: the package version the builder queries, and the identity of the document being edited (its kept-draft key, its save target, the "pinned version" caption, and the pinned-package save path). A host whose package republishes on every change needs those apart. When it pinned the version, every republish orphaned the kept edits and Save went down the pinned path. When it didn't, Edit missed every result the reader had just cached at that version and re-ran every tile.
With queryVersionId set, every query the builder runs uses that version: tiles, the report's manifest, filter options and suggestions, the report listing, and the field catalog. Everything about the document still follows resourceUri alone. So a host passing an unversioned resourceUri plus queryVersionId gets the reader's cached results on Edit, with no second request, while drafts and saving behave as for any unversioned report. A text-held document's compile takes no version, so with textSource only its tiles and options follow the prop. When the prop is unset, behaviour is unchanged.
What's Changed
- chore(release): 0.9.13 by @kylenesbit in #1436
- feat(builder): ReportEditor runs its queries at queryVersionId, apart from the document's version by @kylenesbit in #1435
Full Changelog: v0.9.13...v0.9.14
