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
During porter lint we should resolve the bundle's dependency graph and check for the following problems:
Cycles, the dependency graph will fail to solve when there is a cycle. This is an error.
Unsolvable, the dependency graph fails to find the referenced bundles for each dependency. This can happen when your dependencies are not yet published.
The bundle interface of a dependency is unavailable. This can happen when the bundle interface reference can't be pulled.
The bundle interface cannot be satisfied by the default bundle implementation. This can happen when the bundle reference doesn't satisfy the bundle interface used by the dependency, either because it doesn't have a matching provides declaration as required by the interface, or it doesn't have the right parameters, credentials and outputs.
It is okay for a dependency to declare an interface but not a default bundle implementation.
ℹ️ Read PEP003 - Advanced Dependencies for context about how dependencies should work, design details, and notes about desired behavior.
The text was updated successfully, but these errors were encountered:
During
porter lint
we should resolve the bundle's dependency graph and check for the following problems:It is okay for a dependency to declare an interface but not a default bundle implementation.
ℹ️ Read PEP003 - Advanced Dependencies for context about how dependencies should work, design details, and notes about desired behavior.
The text was updated successfully, but these errors were encountered: