-
Notifications
You must be signed in to change notification settings - Fork 18
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
rename rows to all #16
Comments
Ugh, we've also got Should we just change 1.0.0? :-( |
I think we should. :-( |
Now I'm worried about
vs.
vs.
Perhaps the cognitive obstacle between I've already confused
Now that we have strict checking on The confusion between
By contrast if you were to call In other words, strict
But geez, this whole thing started this morning because I found myself wanting to say
I don't want to get into a holy war over ORMs so I shouldn't care about that factor. The question is what's going to be the most obvious API here and while there's probably not a "right" answer there's righter answers than others. I know it's annoying in CSS that it's Has this cave pinched out yet? |
Reopened for @tshepang. We could use |
Sorry, it was a busy day here at work, so I didn't get a chance to visit this site, but I am quite satisfied with the choice you made... |
Our simple API:
run
/one
/rows
one
androws
aren't parallel. :-(We should either change
one
torow
orrows
tomany
. I likerow
better because it keeps the aliteration andone
andmany
feel ORM-ish to me.Since we've already released 1.0.0 we've got a backwards-compatibility issue. Since we're so early in the project (I released 1.0.0 about 8 or 9 hours ago), I think we can get away with aliasing
row
asone
but not documenting it.The text was updated successfully, but these errors were encountered: