Skip to content

fix: remove internal dotprompt markers from user-facing tools#555

Open
MichaelDoyle wants to merge 1 commit intomainfrom
fix-all-markers
Open

fix: remove internal dotprompt markers from user-facing tools#555
MichaelDoyle wants to merge 1 commit intomainfrom
fix-all-markers

Conversation

@MichaelDoyle
Copy link
Member

@MichaelDoyle MichaelDoyle commented Mar 2, 2026

Removes support for internal <<<dotprompt:...>>> markers from all editor extensions and user-facing tools. These markers were intended for internal processing and should not be exposed to end-users in templates, READMEs, or snippets.

This update affects multiple packages:

  • docs: update design documentation to remove marker references
  • packages/codemirror: remove marker highlighting and stream parser rules
  • packages/emacs: remove marker font-lock patterns and documentation
  • packages/jetbrains: remove marker lexer rules and documentation
  • packages/monaco: remove marker syntax highlighting and theme tokens
  • packages/promptly: remove marker references from design docs
  • packages/treesitter: remove marker from grammar, queries, and corpus
  • packages/vim: remove marker syntax rules and highlighting
  • packages/vscode: remove marker snippets, grammar rules, and README references

Also removes incorrect "block" syntax from role/history helpers in snippets, etc.

@MichaelDoyle MichaelDoyle force-pushed the fix-all-markers branch 5 times, most recently from 85e3643 to 190df26 Compare March 2, 2026 15:31
@github-actions github-actions bot added rust Pull requests that update rust code promptly labels Mar 2, 2026
@MichaelDoyle MichaelDoyle force-pushed the fix-all-markers branch 3 times, most recently from 9c4d29d to 30c8ca5 Compare March 2, 2026 15:55
The primary goal of this change is to strictly remove support for legacy
<<<dotprompt:...>>> internal markers from all authoring environments, as
these are intended for internal runtime use and have been superseded by
the Handlebars helper syntax.

- Remove syntax highlighting and snippet support for internal
  <<<dotprompt:...>>> markers in VS Code, JetBrains, Vim, Monaco,
  and Emacs extensions.
- Clean up dead token types and highlighting attributes in the
  JetBrains and Monaco implementations.
- Update the core Tree-sitter grammar tests to remove legacy marker
  validation.
- Independently transition all role and section snippets from
  block-based ({{#role}}) to inline marker ({{role}}) Handlebars helpers
  to simplify template authoring.
- Restore cursor positioning (bash) and proper newlines to role snippets
  in VS Code to ensure consistent usability.
@MichaelDoyle
Copy link
Member Author

@yesudeep the internal dotprompt markers should be hidden from users. <<<dotprompt.... This PR removes that from all of the IDE integrations, etc. Some syntax/parsing changes came along for the ride.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation editors emacs fix jetbrains js kotlin promptly rust Pull requests that update rust code treesitter vim vscode

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant