-
Notifications
You must be signed in to change notification settings - Fork 39
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
[WIP] Trying to get postgres scaffold work with latest persistent #211
Conversation
You'll need to update the version bounds here, too - that function was introduced after 2.11. You could use |
So you say we better upgrade sooner than later? Then, I'll need to change version boundaries to >= 2.13 && < 3? |
yesod-form also advanced to 1.7.3 which I use and maybe that was the reason for stack resolving to use the incompatible persistent version..... |
The next problem when I try to upgrade to a newer persistent version is this error:
I can't find |
oh, i have the arguments backward, do a |
Thanks @parsonsmatt, now I got it, too. Alright, I pushed a version that seems to work. stack test and build are working. I only slightly changed the package version boundaries to make resolver lts-19.29 and lts-19.30 happy. Should we merge that into postgres branch? And other branches are rebased on that? (Haven't read the complete README yet.) |
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.
LGTM!
This now has a bunch of name shadowing warnings, anyone have thoughts on why that's happening?
|
Oh, I missed that – for me it looks like the template function share causes that. But "share" is not mentioned in the ChangeLog. I have no idea. |
It's this fix which is in 2.14.0.2, but not backported to 2.13. |
OK, so it's good for now and should resolve at the next upgrade (as soon a new LTS is available and the bounds on |
Great, thanks! I've pushed the changes to the stack-templates repo. |
Fixes #210
Thanks for your help @snoyberg and @parsonsmatt!
Now that I tried the current scaffold from scratch, I found that it works because persistent-postgresql have correct bounds in
package.yml
(<2.11). Maybe I just apply this bounds in my projects, too.I still created this PR as a basis for a future upgrade to a newer version of persistent. Hope that helps.