matej/vscode-diagnostics-comment-awareness

[voiys]

Summary

• only treat comment lines as decorator-bearing when the comment body starts with @
• stop regular comments that merely mention @decorator or @type=... from triggering VS Code diagnostics/type validation
• add regression coverage for both regular-comment cases

Test plan

• bunx vitest packages/vscode-plugin/test/diagnostics-core.test.ts
• bun run lint:fix

Examples:

1. Regular comments are ignored (intellisense does not trigger either, can turn that off if you want)

2. Post-comments on decorator lines are ignored

3. Real decorator diagnostics still work

4. Real type diagnostics still work, but commented trailing type text does not

[changeset-bot]

🦋 Changeset detected

Latest commit: d9f9160

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
env-spec-language	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[theoephraim]

Not sure about this. The real loader will explode when it sees this with an "unknown decorator" kind of error. Maybe we should allow them as noops since they are common though. But either way it should match.

[theoephraim]

you can add a changeset with the vscode extension tagged. It will merge them all up when we publish together

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/varlock@467

commit: d9f9160

[voiys]

VS Code now matches parser behavior here: prose mentions/post-comments are ignored, but leading @word comment lines still parse the same way the parser does