Provide ediTDor as npm package

[gintephSICKAG]

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:

• ediTDor could be used inside other projects
• the viewer could be used as a standalone component

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?

[hadjian]

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!

[gintephSICKAG]

Thank you for response @hadjian!

These ideas sound great to me and would significantly enhance our Thing Descriptions/Thing Models tooling. I'm looking forward to reading the design doc and providing feedback.

[hadjian]

@gintephSICKAG Great! A first draft should be available tomorrow. I'll ping you then.

[hadjian]

@gintephSICKAG as promised: https://github.com/web-of-things-open-source/proposal/issues/2

I added you to the organization, so you can comment.