Remove JSON registry stuff #5
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The JSON registry is really the bridge's concern, and not inherent to the WCLAP format.
Instead of maintaining an official CLAP registry which attempts to be universal, the bridge can be pre-configured with a default registry of WCLAPs, just so there's something to use when first opened. Instead of discovering new plugins through the repository, they'd find 3rd-party repositories through other means, and add them via URL.
However, I do still like the idea of recommending
.tar.gzbundles for downloading (since it helps compatibility, even if the repository format supports additional archive formats later), so I've kept that part.