Skip to content

cabal: Also increase transformers version in the tests#19

Merged
Gabriella439 merged 2 commits intoGabriella439:mainfrom
rvl:cabal-bounds-transformers
Oct 1, 2024
Merged

cabal: Also increase transformers version in the tests#19
Gabriella439 merged 2 commits intoGabriella439:mainfrom
rvl:cabal-bounds-transformers

Conversation

@rvl
Copy link
Contributor

@rvl rvl commented Sep 19, 2024

The library component has transformers <0.7 but the test-suite component had transformers <0.6.

I was wondering, would it be better to remove version bounds from every build-depends in the test-suite and executable components where:

  1. the library component also has that library as a build-depends, and
  2. the bounds should not be less than what is given in the library component, and
  3. the test-suite or executable has a dependency on the library component.

Thanks

The library component has transformers <0.7 but the test-suite
component had transformers <0.6.
@Gabriella439
Copy link
Owner

Yes, I usually do that for my other packages already. The only reason that pipes-extras doesn't do it that way is because I created this package before I learned the trick of centralizing bounds mostly in the library target.

I'd accept a PR to remove those test bounds

Some build-depends of the test-suite component already have their
version bounds constrained by the library component, so remove those
bounds to ease maintenance.
@rvl
Copy link
Contributor Author

rvl commented Oct 1, 2024

OK done, thanks @Gabriella439.

@Gabriella439 Gabriella439 merged commit f2e76df into Gabriella439:main Oct 1, 2024
@Gabriella439
Copy link
Owner

You're welcome! Also, thank you!

I published a matching revision to Hackage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants