Name conflict dodges #365
Merged
Name conflict dodges #365
Conversation
This file contains hidden or 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
parsonsmatt
commented
Jun 8, 2023
Comment on lines
+268
to
+269
| groupBy_ :: (ToSomeValues a) => a -> SqlQuery () | ||
| groupBy_ = groupBy |
Collaborator
Author
There was a problem hiding this comment.
To me, the main question is: do we want to deprecate the other function names at some point and only have these _ suffixes?
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.
This PR adds
isNothing_,groupBy_, andupdateEas "non-conflicting" variants of the other esqueleto functions. This helps avoid name conflicts and makes it easier to importesqueletowith other libraries.Before submitting your PR, check that you've:
@sincedeclarations to the Haddock.stylish-haskelland otherwise adhered to the style guide.After submitting your PR: