Repository navigation
feat: support Django and Jinja language identifiers - #67
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d4423ad0dc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
🟡 Changes recommended
Native path normalization makes the new validator fail on Windows.
1 open finding
What changed in this PR
Adds snippet support for Django and Jinja language identifiers while preserving HTML behavior.
Changes:
- Registers six additional language/catalog mappings.
- Validates manifest registrations and framework separation.
- Documents supported language modes and recognition requirements.
| File | Description |
|---|---|
package.json |
Registers snippets for Django and Jinja modes. |
scripts/validate-snippets.js |
Validates snippet registrations and paths. |
README.md |
Documents supported modes and extensions. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Template files recognized as
django-html,jinja, orjinja-htmlcurrently have no Python Template Snippets contributions. Add the six missing registrations while preserving all three HTML registrations and all snippet definitions.Closes #44.
htmldjango-htmljinjajinja-htmlpackage.json: register the existing catalogs under the appropriate language IDs.scripts/validate-snippets.js: validate supported, nonempty language IDs, real file paths, duplicate mappings (including normalized paths), required mappings, and framework separation without depending on entry order.README.md: document supported modes and the language extensions needed for recognition.Language IDs were checked against the Django manifest, Jinja manifest, and Better Jinja manifest. VS Code uses manifest language contributions as the default scopes for these catalogs, so existing snippet-level
scopevalues require no changes.Validation:
npm ci --cache ../npm-cache: passed using the existing lockfile. A writable cache was needed in this environment. npm reports two existing development dependency advisories; dependencies and lockfile are unchanged.npm test: passed; 3 catalogs, 30 prefixes, 9 registrations.npx vsce package: passed. The packaged manifest matches the source manifest, and every packaged snippet catalog matchesmainbyte-for-byte.git diff --check: passed.Relationship to #3:
.j2files benefit when a language extension recognizes them asjinjaorjinja-html(or another supported mode). This does not implement arbitrary filename-pattern activation, add language definitions, or override file associations. #3 remains separate and open.No version bump, release, Marketplace publication, or release tags.