Skip to content

Editor: policy expressions, Go to Definition for every declaration, and spell words - #1088

Merged
einari merged 1 commit into
mainfrom
screenplay-editor-gaps
Oct 28, 2026
Merged

einari merged 1 commit into
mainfrom
screenplay-editor-gaps

Conversation

@einari

@einari einari commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Added

  • Go to Definition in the VS Code extension for any name a model declares: a concept, policy, command, read model, query, screen, screen or dialog template, form, behavior, trigger and the rest, in whichever file of the folder application declares it.
  • The extension's spelling dictionary knows stateview and statechange, so scopes slice stateview is not flagged by Code Spell Checker.

Fixed

  • The editor no longer reports and, or or not in an authorize expression as an unknown policy, and reads parenthesized and multi-line expressions the way the compiler does. authorize IsProgramCommittee and IsInReviewWindow compiled but showed a warning in the editor.

@einari einari added minor New features, non-breaking additions ai-corpus: none Language change that does not affect the AI corpus (reason stated in a PR comment) labels Oct 28, 2026
@einari

einari commented Oct 28, 2026

Copy link
Copy Markdown
Contributor Author

Corpus impact: none - this changes only what the VS Code extension and editor language service report and navigate to; no language construct, diagnostic code or generated output changes.

@einari
einari merged commit 5e53e04 into main Oct 28, 2026
18 of 20 checks passed
@einari
einari deleted the screenplay-editor-gaps branch October 28, 2026 05:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-corpus: none Language change that does not affect the AI corpus (reason stated in a PR comment) minor New features, non-breaking additions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant