eclipse-thingweb / td-tools Goto Github PK

Note: coming from #7 (comment)

I noticed some shortcoming w.r.t. to the current setup.

• in node-wot we used to have eslint-plugin-unused-imports. I think having this might be useful
• I also noticed that "npm run lint" does not screem if I have unused variables in my code. Useful again I think.
• I also wonder whether prettier & linting should be based on language level (hence moving it into the /node directory )

I noticed that async-api-converter uses the following folder structure

• examples
• src
• tests

I wonder whether we want to decide on a folder structure. The question for me is for example whether it should be "tests" or "test" as we use in other repos like node-wot td-tools.

          We will create a package in td-tools that has such helper functions and then deprecate the functions here. Also, the function in https://github.com/eclipse-thingweb/playground/blob/master/packages/core/index.js#L1293 will be moved there and published. It can be more flexible with some filters like "find it only in properties".

td-utils will be the new package name and can contain such tools. It should return an object with binding name as keys (just http, opc etc) then inside it found uri scheme (http, https, mqtt+ws) and subprotocol.

Originally posted by @egekorkan in eclipse-thingweb/node-wot#1270 (comment)

Some possibilities are (might be?)

• use dist folder
• look at https://github.com/EsotericSoftware/spine-runtimes/tree/4.1/spine-ts

relates to #7

We have to decide:

• the npm root name and the subprojects.
• README already mentions a list of possible projects but what is the directory structure?
• Is gitsubmodules still an option? or npm workspaces?
• Understand dependencies between tools

As demonstrated with #15 there is no CI check that shows test or build failures.

https://github.com/eclipse-thingweb/td-tools/blob/main/README.md informs about the idea to move certain projects.

Since some tools exists already we ought to update the README