🐛 Classify the two token change types develop added

develop replaced :set-active-token-themes with :set-tokens-status, which
writes the active theme and set ids into :tokens-status, and added
:set-tokens-source, which points a file at an external tokens library.
the-classification-table-names-every-change-type fails by name on both,
which is what it is for.

Both are no-ops for the overlay. The builder indexes token sets and
tokens from the file's own :tokens-lib and stores no active status, and
it reads that lib whatever :tokens-source says, so neither change can
reach a datom a rebuild would write.

AI-assisted-by: claude-opus-5-5
This commit is contained in:
Álvaro Tejero Cantero 2026-10-04 00:35:36 +02:00
parent 1c4d3580d4
commit e91b70775d
No known key found for this signature in database

View File

@ -644,8 +644,9 @@
:mod-media {:coverage :no-op :why "the same reason as an add's"}
:del-media {:coverage :no-op :why "the same reason as an add's"}
:set-token-theme {:coverage :no-op :why "themes are not indexed"}
:set-active-token-themes {:coverage :no-op :why "the active theme set is not indexed"}
:set-base-font-size {:coverage :no-op :why "file options are not indexed"}})
:set-tokens-status {:coverage :no-op :why "the active theme and set status is not indexed"}
:set-base-font-size {:coverage :no-op :why "file options are not indexed"}
:set-tokens-source {:coverage :no-op :why "the builder reads the file's own `:tokens-lib` whatever the source, so pointing the file at a library writes no datom"}})
(def ^:private operation-coverage
"One row per member of `app.common.files.changes/schema:operation`, the