Skip to content
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

Open
gintephSICKAG opened this issue Jun 20, 2022 · 4 comments
Open

Provide ediTDor as npm package #77

gintephSICKAG opened this issue Jun 20, 2022 · 4 comments

Comments

@gintephSICKAG
Copy link

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
Copy link

hadjian commented May 5, 2023

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
Copy link
Author

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
Copy link

hadjian commented May 31, 2023

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

@hadjian
Copy link

hadjian commented Jun 1, 2023

@gintephSICKAG as promised: wot-oss/proposal#2

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants