Skip to content

Conversation

@callzhang
Copy link

  • 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 (v1.0.0).
  • 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. (Not
    needed for current minimal payload; can add if requested.)

My package is Sublime Text commands to auto-decode messy text (URL/HTML/unicode/hex/base64/gzip) and fix/pretty-
print JSON, with full-buffer fallback when nothing is selected.

There are no packages like it in Package Control.

@braver
Copy link
Collaborator

braver commented Dec 18, 2025

The package itself looks mostly just fine. However, you should separate your Sublime Text package from the web interface somehow. As it is, all the web stuff including the installation script will be shipped as part of your package. It probably won't do anything, but it's a little messy and might become a problem later. Perhaps these things could be different repositories altogether (I don't imagine they share much). Or you could use .gitattributes to export-ignore the web-specific bits.

@braver braver added the feedback provided The changes and package have been seen by a reviewer label Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feedback provided The changes and package have been seen by a reviewer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants