Skip to content

Conversation

@kaessajidi
Copy link

@kaessajidi kaessajidi commented Oct 25, 2025

  • I'm the package's author and/or maintainer.
  • I have have read the docs.
  • I have tagged a release with a semver version number.
  • My package repo has a description and a README describing what it's for and how to use it.
  • My package doesn't add context menu entries. *
  • My package doesn't add key bindings. **
  • Any commands are available via the command palette.
  • Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
  • If my package is a syntax it doesn't also add a color scheme. ***
  • I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

My package is a specific 3DEXPERIENCE language syntax

removed package.json
@kaessajidi kaessajidi requested a review from braver October 29, 2025 10:39
"packages": [
{
"details": "https://github.com/kaessajidi/ekl-sublim-text",
"name": "Dassault Systemes EKL Syntax",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"name": "Dassault Systemes EKL Syntax",
"name": "Dassault Systemes EKL",

Language support packages don't need to have "syntax" or something like it in the name, since typically it does more than just the syntax: in your case it also provides completions (which you might want to specify in the labels).

If you want to call it Dassault Systemes EKL and not just EKL, it should go into the d.json file instead, an in alphabetical order there.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants