Closed relu91 closed 6 days ago
node-packages
, python-packages
. We do not have multiple languages at the moment but it is good to have stable links for the future.validators
folder and then node
and python
folders within them.@danielpeintner will detail what the other scripts within node-wot/td-tools do
Please find below a proposal how to restructure "td-tools" related code:
eclipse-thingweb/node-wot/packages/td-tools
entirelyeclipse-thingweb/node-wot/packages/core
should link to eclipse-thingweb/td-tools/node/foundation
(see newly created package below)eclipse-thingweb/td-tools/node/foundation
(all open for a better name) witheclipse-thingweb/td-tools/node/thing-model
witheclipse-thingweb/td-tools/node/aid
withAny opinions/suggestions?
I quite like the proposal. The main confusing part is how to explain what the "foundation" package offers to outsiders so I am not able to provide an alternative name :/
@eclipse-thingweb/td-tools/thing-model-helpers
@thingweb/td-tools/thing-model-helpers
-> may not be allowed@thingweb/td-tools-thing-model-helpers
@thingweb/thing-model-helpers
@thingweb/tm-helpers
@thingweb/node-wot-binding-http
@thingweb/node-wot-contrib-binding-x
@
is not governed or restricted but we should checkDecision on renaming: we will have @thingweb/TOOL_NAME
When will the new structure be applied?
When will the new structure be applied?
In the meantime, @relu91 or @danielpeintner, could you document here or in node-wot how the td-tools are used within it? I think we need better understanding before committing to a direction.
I sketched how I "see" the best way forward in https://github.com/eclipse-thingweb/td-tools/issues/3#issuecomment-1816398949 We (I) can try to describe next year ;-) the relations and it current usage...
node-wot td parser: Consuming:
For the future, the core package can do this, meaning td-parser is not necessary for an outsider as a tool
The overall structure is now applied. I will open new issues for default handling and validation
We have to decide:
gitsubmodules
still an option? or npm workspaces?