Import stackage as dev-dependency #1968
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mark the stack_snapshot imports within rules_haskell itself as dev_dependencies.
Otherwise downstream users of rules_haskell will have the same packages imported into their Stackage snapshot as used by rules_haskell for testing purposes. This can cause problems if downstream users want to use a different Stackage snapshot that may not include one of the dependencies imported by rules_haskell.
Note, due to a reference to
@stackage
from within thestack_snapshot
implementation we still need to import the repository@stackage
in all cases. This is done by using separate references to the extension, one marked as dev-dependency and the other not. However, they both refer to the same underlying instance of the module extension.