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
It doesn't cause failures for bazel since rules_haskell unify names and allows for a duplicates (but which shouldn't happened as confirmed with @aherrmann - defect is pending and will be added here).
Expected behavior gazelle-update-repos should try to avoid generating duplicates while updating packages list of the stack repository when one of the packages has #keep comment. Maybe gazelle_cabal should produce additional warning about such case.
Describe the bug
gazelle-update-repos
can generate duplicates withinstack_snapshot::packages
when one of the packages has "strict" versioning.To Reproduce
stack_snapshot::packages
list, e.g.haskell_library
contain following entry:...
3. ..., then running
:gazelle-update-repos
will generate duplicates withinstack_snapshot::deps
It doesn't cause failures for bazel since
rules_haskell
unify names and allows for a duplicates (but which shouldn't happened as confirmed with @aherrmann - defect is pending and will be added here).Expected behavior
gazelle-update-repos
should try to avoid generating duplicates while updating packages list of the stack repository when one of the packages has#keep
comment. Maybe gazelle_cabal should produce additional warning about such case.Environment
Additional context
Observed while converting example-servant-elm to bazel. There are two places from which those dependencies come:
The text was updated successfully, but these errors were encountered: