I'm clear on the new Library Manager (Repositories, Space Lua, etc.), but I'm confused about the current workflow for legacy Plugs that aren't libraries yet.
My Command Palette only shows Library:* commands. There are no Plugs:* commands to add or manage extension URLs, and the centralized SETTINGS page is no longer used.
My questions:
What is the recommended way to install a legacy .plug.json via URL in SB v2?
Is using a decentralized page with tags: meta/config and a plugs: YAML block the intended replacement for the old settings?
Should we still use the _plug/ folder, or is there a way to keep it purely URL-based/declarative?
I want to avoid manual file management to keep the space clean. Thanks!
I'm currently replacing the Library Manager with a complete new UI. Getting close to shipping it. This should also address a few of your issues:
Recommended way to install legacy plugs in v2: There will be a button to install a library or plug via its full URL. There you can simply drop in the URL to the file (e.g. on Github) and it will work
yes, this is now decentralized. There is technically (still although I'll also remove it as part of this change) config with a list of plugs that Plugs: Update updates, but this part is also legacy. The new setup is: if you have a .plug.js file somewhere in your space, it will be loaded. And the new Configuration Manager UI will make it more transparent.
The _plug folder is also legacy and has no special meaning anymore already for a while.
Are there specific legacy plugs you have in mind? I can also remind them to add a proper Library wrapper if their plugs are still maintained.