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
If libA depends on libB, it will now infinitely query the dependencies of libB (since it refers to itself indirectly).
One solution that doesn't create inflexibility is a configurable maximum depth for the dependency tree, in order to catch this easier. Other options (like checking the haxelib.json content name vs the haxelib name) might work as well.
The text was updated successfully, but these errors were encountered:
consider:
haxelib git libA <libA url>
haxelib git libB <libA url>
If libA depends on libB, it will now infinitely query the dependencies of libB (since it refers to itself indirectly).
One solution that doesn't create inflexibility is a configurable maximum depth for the dependency tree, in order to catch this easier. Other options (like checking the haxelib.json content name vs the haxelib name) might work as well.
The text was updated successfully, but these errors were encountered: