Correction when defining the boundaries of each dependency #177
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#174
In this update, we fixed an issue related to defining version constraints for dependencies across different sections of the .cabal file. Originally, version constraints for certain dependencies were defined in multiple sections, including library, executable, and test-suite. However, following best practices and the project owner's recommendation, these constraints are now defined in a single section, allowing the constraints to be automatically inherited by the other sections. This simplifies the .cabal file and ensures more efficient dependency management.
Specific changes include removing redundant version constraints in the executable and test-suite sections, keeping only the constraints in the library section as the reference point for other sections. This improves the clarity and maintainability of the .cabal file.