pearl/tests/test-pearl-local-views.el, branch mainPearl Edits and Reflects Linear — manage Linear.app issues as org-mode in Emacs
https://git.cjennings.net/pearl/atom?h=main2026-06-01T23:05:52+00:00feat(views): guard publish and delete against cross-account local views2026-06-01T23:05:52+00:00Craig Jenningsc@cjennings.net2026-06-01T23:05:52+00:00urn:sha1:96ac9855cfda77f81d7f12e55d737e8bdd54eccc
I extended the account guard from edit and run to the two remote-mutating commands. pearl-publish-local-view now refuses a local view tagged to another account before any customViewCreate or customViewUpdate, and pearl-delete-local-view refuses before the confirm prompt or any customViewDelete. Publishing or deleting under the wrong account would resolve ids against the wrong workspace or target the wrong remote, so the guard fires at the command boundary, before Linear is touched. publish-current-view inherits the guard by delegating to publish-local-view.
This completes the round-6 finding that one guard should cover every read and mutate of a local-view entry, not only edit and copy.
Phase 5 of the views spec. Tests confirm both commands error on a cross-account entry and make no Linear call. Suite, compile, and lint are green.
feat(views): add create and edit local views with a metadata-preserving writer2026-06-01T22:46:34+00:00Craig Jenningsc@cjennings.net2026-06-01T22:46:34+00:00urn:sha1:6206fde5acfd48f9eba2ab231c1fe1d32717c98e
I added pearl-create-local-view and pearl-edit-local-view, plus the writer and guards the spec calls for. pearl--save-local-view replaces the old rebuild-from-scratch writer. It copies an existing entry and updates only the filter, sort, and order, so a published view keeps its :linear-view-* tracking link and a copied-down view keeps its provenance. A new entry gets the active account stamped under pearl-accounts.
pearl--require-local-view-account is the one guard every read or mutate command shares, and pearl-run-local-view now calls it instead of an inline check. pearl--resolve-local-view-name carries the Replace/Rename/Cancel collision policy for create, edit-rename, and copy-down. The ad-hoc builder's save offer routes through the preserving writer and reads "save this as a local view".
Edit re-runs the builder when you choose to rebuild and otherwise keeps the stored filter. Full per-dimension pre-seeding of the builder is deferred, since it needs the id-to-name reverse resolution that copy-down's reverse-compile introduces. I filed it as a follow-up.
Phase 2 of the views spec. Tests cover metadata preservation, the account guard, the collision policy, and the metadata-preserving rename. Suite, compile, and lint are green.