-
-
Notifications
You must be signed in to change notification settings - Fork 413
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
Renamed AtLeastOneFragment
type class to AtMostOneFragment
#1727
Conversation
AtLeastOneFragment
to AtMostOneFragment
AtLeastOneFragment
type class to AtMostOneFragment
@jkarni would you mind giving your opinion on this? |
@DavidMazarro Thanks for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
(I added these last two commits because I was unfamiliar with |
Feel free to run the CI on this one again, but other than that it's ready to merge from my side :) |
@tchoutri could you run the CI workflow again? |
Alright, I have looked up the usage of Thanks @DavidMazarro! |
Unless I'm misunderstanding the
FragmentUnique
type family, it's checking that there's at most one fragment in the API type. In that case, theAtLeastOneFragment
name is not only confusing, but potentially misleading. This PR renames the type class toAtMostOneFragment
.In addition, I did some small changes to the documentation, I moved the explanation of the type class to the type class definition (previously the comment was under the
Verb
instance) and reworded it a bit.