Repository navigation
Enhanced Graph 1.1.1
A submission-review fix release. The plugin behaves exactly as 1.1.0 does; what
changed is what the directory's automated review found.
The blocking error
The review failed 1.1.0 on one error:
Sets styles directly instead of using CSS classes,
setCssProps, or
setCssStyles—harness/official-filters.ts:122
The test harness positions the stand-in built-in graph with an inline
style.cssText. The harness is scanned like the rest of the repository, so a
static style assignment there is an error even though no user ever runs it. The
box now comes from the harness page's own stylesheet
(.harness-official-graph), and the script only sets the class name.
Recommendations cleared
- Release assets now carry build provenance. The release workflow attests
main.jsandstyles.csswithactions/attest-build-provenance, so anyone can
verify withgh attestation verifythat the files were built from this
repository by that workflow, rather than uploaded by hand. - No more unsupported extra asset.
THIRD-PARTY-NOTICES.mdwas published as a
fourth release asset; Obsidian never downloads it and the directory flags it.
The file stays in the repository, and the notices also travel in the bundle's own
footer, so nothing about attribution changed.
Dead code the review noticed
Four leftovers from 1.1.0's removals, each an import or binding nothing used any
more: renderWeights in the built-in graph's module, DEFAULT_RELEVANCE_WEIGHTS,
GraphNode and GraphSnapshot in the plugin entry point, and the unused result of
applyExternalLayout.
Not changed
The review's remaining items are recommendations and warnings that this plugin
cannot honestly clear: it enumerates the vault because a vault-wide graph is what
it draws, and it reads the clipboard because one command copies the relevance
report. Both are listed as recommendations, not errors, and the same entries were
present on 1.0.2, which the review completed.