Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix type error message with AtLeastOneUniqueKey class #1544

Merged
merged 2 commits into from
Aug 28, 2024

Conversation

parsonsmatt
Copy link
Collaborator

Before submitting your PR, check that you've:

  • Documented new APIs with Haddock markup
  • Added @since declarations to the Haddock
  • Ran stylish-haskell on any changed files.
  • Adhered to the code style (see the .editorconfig file for details)

After submitting your PR:

  • Update the Changelog.md file with a link to your PR
  • Bumped the version number if there isn't an (unreleased) on the Changelog
  • Check that CI passes (or if it fails, for reasons unrelated to your change, like CI timeouts)

@@ -2306,7 +2306,7 @@ mkUniqueKeyInstances mps entDef = do
typeErrorAtLeastOne :: Q [Dec]
typeErrorAtLeastOne = do
let impl = mkImpossible requireUniquesPName
cxt <- typeErrorMultipleCtx
cxt <- typeErrorNoneCtx
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoops lmao


* [#1544](https://github.com/yesodweb/persistent/pull/1544)
* Fix type error message when no unique keys are defined on a model and you
use a function with constraint `AtLeastOneUniqueKey`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW this popped up with another function I was using but it looks to come from the same place

@parsonsmatt parsonsmatt merged commit 24f5d92 into master Aug 28, 2024
9 checks passed
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