Repository navigation
feat!: annotationsFrom takes structured-context's issue list - #32
Merged
Merged
Conversation
structured-context 0.23 reports validation as one `issues` list, each issue
with its kind and severity, and drops nodeIssues. annotationsFrom now takes
{ issues } as a ValidationResult or `sctx validate --json` gives it, so either
can be passed as it is.
UnattachedAnnotation's line/column become `location` (a SourceLocation), so a
parse issue keeps its file. 'parse' joins the validationSources enum, which
follows core's VALIDATION_ISSUE_KINDS.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019Xphpde5yiQF1dWi3KfETS
mindsocket
commented
Nov 10, 2026
mindsocket
left a comment
mindsocket
left a comment
Owner
Author
There was a problem hiding this comment.
Work needed to simplify docs and code comments
…kinds from core Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Xphpde5yiQF1dWi3KfETS
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Rog · project thread
Follows mindsocket/structured-context#217 (released in 0.23.0). That release reports validation as one
issueslist, where each issue carries its kind and severity, and it dropsnodeIssues.What
annotationsFrom({ issues }, graph)reads the list. You can pass aValidationResultorsctx validate --jsonoutput as it is. There's no separateruleViolationsinput any more.UnattachedAnnotation,line/columnbecomelocation(aSourceLocation), so a parse issue keeps its file. The navigator's "Not on a node" panel now groups by node, then by file.nodes.validationSourcesgainsparse, because it follows core'sVALIDATION_ISSUE_KINDS. The generated schemas are regenerated.structured-context ^0.23.0.exportSnapshotand the navigator passissuesstraight through.Checks
bun test(78 pass),bun run typecheck,bun run lint. I couldn't runbun run buildandtest:packageto the end here, because the sandbox blocks jsDelivr. The library build itself succeeded.Breaking for hosts, so this should be a minor release (0.6.0). After it's published, the core plugin's map pane can drop its
PROTOTYPE:adapter.Generated by Claude Code