-
Notifications
You must be signed in to change notification settings - Fork 148
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
Ecto 2.0 support #112
Comments
I can make a PR in preparation, but I'm not sure how far off Ecto is to releasing. Also scrivener is awaiting an update too. |
Ok, I've made a PR to Scrivener to add support for Ecto 2.0.0-rc (see mojotech/scrivener#36). I'll just work off the cultureamp branch for now, and make a PR. As I said on the Scrivener PR, I don't expect it to be merged, but perhaps some people might find it useful! |
Hi @bjz thanks for opening this issue. The existing codebase should work just fine with Ecto 2.0+, In all honestly I would like to get rid of the dependency completely if I can figure out how. Until 2.0 is actually released you can just override the ecto dep in your project: {:ecto, "2.0.0-rc5", override: true} You can probably do the same with scrivener, but I haven't upgraded a project using scrivener to ecto 2.0 yet. |
Oh cheers, didn't know about dependency overrides. Still getting a handle on mix! It does seem that there is a branch out for scrivener that supports ecto 2.0: mojotech/scrivener#36 (comment) |
I'll try that tomorrow tomorrow at work, then let you know how it goes. |
This seems to work: defp deps do
[
{:ecto, "~> 2.0.0-rc", override: true},
{:ja_serializer, "~> 0.9.0"},
{:phoenix_ecto, "~> 3.0.0-rc"},
{:scrivener, git: "https://github.com/drewolson/scrivener.git", branch: "v2", override: true},
# ...
]
end |
Great! |
Now that 2.0 is out this shouldn't be an issue! |
Ok, so the Ecto 2.0.0-rc is out. Would it be much trouble to get ja_serializer up and running with it? There are some features we would really love to use in the new Ecto version :)
The text was updated successfully, but these errors were encountered: