Implement interactive list of plugins, settings component demo, and visual SettingsTemplate.yaml editor #82
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.
This PR implements an interactive list of plugins that replaces the old one that was previously being updated by the GitHub workflow. It also includes demos of how different fields from SettingsTemplate.yaml look, and a visual editor for SettingsTemplate.yaml
It is written with Svelte and compiles to native Web Components, so the only thing needed for it to work is to include the built script into the page and use one of the components. Currently it exposes 3 web components:
<plugin-directory></plugin-directory>— the interactive plugin directory.<settings-generator></settings-generator>— the visual editor for theSettingsTemplate.yamlfile for JSON-RPC plugins (Demo)<settings-component-demo></settings-component-demo>— this provides imitations of different types of fields available in SettingsTemplate.yaml so the users would be able to see how they look without having to create a plugin first (Demo)Unfortunately, I don't know if it's possible to test GitHub actions in PRs without merging them. I hope I got everything right with the token and stuff.
The workaround with the new
<script>tag is there because I couldn't find a way with Docsify to include<script src="..." type="module">, it would just not execute it.