It would be very nice to have dependency manifest from given module which could be then injected and scanned from out of module using depin. Actually it is must to have as clients of Depin dependency modules, are not able to find them in any other way than inspecting code. So less dependency naming collision would be introduced.
This could be implemented with runnable module where user would input name of module to create manifest for. Manifest would have to be available from docs of module or package.
Should it be automatic process ? So docs would be added automatically to clients modules ?
If not how to represent such documentation for user to be used put it in resources? As json ? xml ?
It would be very nice to have dependency manifest from given module which could be then injected and scanned from out of module using depin. Actually it is must to have as clients of Depin dependency modules, are not able to find them in any other way than inspecting code. So less dependency naming collision would be introduced.
This could be implemented with runnable module where user would input name of module to create manifest for. Manifest would have to be available from docs of module or package.