Right now the dependencies doc is a bit lean on use-cases and doesn't tell you everything you'd need to know about using and debugging dependencies (e.g. there's no mention of how dependencies are resolved or the architect link command). The dependencies doc should be more use-case driven so developers know when to use them and whats happening under the hood.
Right now the dependencies doc is a bit lean on use-cases and doesn't tell you everything you'd need to know about using and debugging dependencies (e.g. there's no mention of how dependencies are resolved or the architect link command). The dependencies doc should be more use-case driven so developers know when to use them and whats happening under the hood.