Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Phase out requirement for .no-sublime-package #22

Open
FichteFoll opened this issue Jul 23, 2019 · 2 comments
Open

Phase out requirement for .no-sublime-package #22

FichteFoll opened this issue Jul 23, 2019 · 2 comments

Comments

@FichteFoll
Copy link

As discussed in wbond/package_control_channel#7612, it would be nice if this file wasn't needed. This issue is to track progress and alternatives. Feel free to ask me or Thomas, if you're running into a wall or are curious about things.

@rchl
Copy link
Contributor

rchl commented Nov 14, 2021

@daveleroy Do you think it would be fine to store adapters in "Package Storage" (as coined by LSP) and the sublime package schema in User/Debugger.sublime-package?

Not sure if there are any other things that would need to be changed.

@daveleroy
Copy link
Owner

There probably needs to be some more changes here than just switching where things are stored.

There is no auto update of adapters and storing them inside the package means they get removed when things get updated so users have to get the latest versions after an update.

Things like breakpoints and watch variables also get stored inside the package. The schema for these would need to either remain backwards compatible or have some sort of version information tied to them so they could be invalidated

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

No branches or pull requests

3 participants