-
Notifications
You must be signed in to change notification settings - Fork 3
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
Project structure and package name #3
Comments
|
@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:
Any 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 :/ |
Decision on renaming: we will have |
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 #3 (comment) |
node-wot td parser:
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?The text was updated successfully, but these errors were encountered: