feat: add sublime-breadcrumb plugin

[huyhoang8398]

• I'm the package's author and/or maintainer.
• I 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.

A clean breadcrumb that shows both the file path and the current symbol hierarchy at the top of the editor. Powered by the LSP plugin for accurate

[github-actions]

Package Review

Channel Diff

Removed (none), changed (none), added Sublime-Breadcrumb.

Review for Sublime-Breadcrumb main-bcd5e18-2026.03.30.12.55.53

No notices

1 failures:
- No semantic version tags found (no tags found at all)
    Repository: https://github.com/huyhoang8398/sublime-breadcrumb

No warnings


For more details on the report messages (for example how to resolve them), go to:
https://github.com/packagecontrol/st_package_reviewer/wiki

[kaste]

Yeah.

    "sublime_text": ">3084"

is probably unrealistic as you require LSP.

We don't have best in class solution for this. You could name the plugin LSP-addon-... to make that more clear. But you can also really write the code a bit more pessimistic:

Maybe do a try import LSP at the global scope and catch the ImportError; and if you catched it let the event handler do nothing. Or even just print a message to the console and don't register any of the extension names, no Command no EventListener.

Register an install.txt message that clearly says: "This is an addon to LSP"/"Attention: this requires LSP and does this...".