-
Notifications
You must be signed in to change notification settings - Fork 19
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
Provide ediTDor as npm package #77
Comments
Hi @gintephSICKAG! Sorry for the very late response. We're picking up work on the project again and the idea is quite good. Out of those components, we could make a vscode package with editor and viewer. We're floating around the idea to make a language server to support more complex auto-completions like support for inheritance and composition, ontologies and more. Stay tuned for a design doc, although this might take a while... Like to get your feedback! |
Thank you for response @hadjian! These ideas sound great to me and would significantly enhance our Thing Descriptions/Thing Models tooling. |
@gintephSICKAG Great! A first draft should be available tomorrow. I'll ping you then. |
@gintephSICKAG as promised: wot-oss/proposal#2 I added you to the organization, so you can comment. |
It would be great if ediTDor could be split up into two standalone npm packages. One package for the viewer part and one providing the editor+viewer (analogue to swagger-ui and swagger-editor).
This would give us some greater flexibility:
I do see some difficulties in splitting up the components due to the usage of one global React Context. But a simpler solution could be to build only one ediTDor package and provide some configuration for hiding the editor part (something like a read only mode).
What do you all think about this idea?
Does anyone else have such requirements or might be interested in such a solution?
The text was updated successfully, but these errors were encountered: