You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As all changes proposed in the initial issue were reported as addressed, it's now our task to update the integration and make it dynamic (so whenever document-model-libs is updated, documentation is also updated automatically)
not sure what the requirement remove initial static md files means in the issue. Could you elaborate what here is wrong if it is?
When writing the issue I thought that we kept initial md files provided to us and already executed generateDocs.ts somewhere during frontend build in order to produce content/documentation/index.md file. Now I see it's not the case, this particular point can be ignored.
What I would expect nevertheless, is that content/documentation/index.md file is produced automatically from the npm package and doesn't need an additional action from the developer (ie manually running generateDocs.ts and then committing generated file is not a desired flow)
Goal
Implement dynamic
document-model-libs
documentationContext
As all changes proposed in the initial issue were reported as addressed, it's now our task to update the integration and make it dynamic (so whenever
document-model-libs
is updated, documentation is also updated automatically)Tasks
document-model-libs
as npm packagegenerateDocs
scriptnode_modules
)The text was updated successfully, but these errors were encountered: