No longer working with Ecto 2.0-beta

[johnhamelink]

Hey there,

The breaking changes introduced in 2.0-beta have caused params to break (thankfully its tests also break in the same way). I'm working on a PR to fix this right now, but in the meantime, here's the sort of errors I'm experiencing:

Compiled lib/params/def.ex
** (Protocol.UndefinedError) protocol Enumerable not implemented for :id
    (elixir) lib/enum.ex:1: Enumerable.impl_for!/1
    (elixir) lib/enum.ex:116: Enumerable.reduce/3
    (elixir) lib/enum.ex:1486: Enum.reduce/3
    test/params_test.exs:10: (module)
    test/params_test.exs:8: (module)

== Compilation error on file lib/params.ex ==
** (CompileError) lib/params.ex:77: unknown key :model for struct Ecto.Changeset
    (elixir) src/elixir_map.erl:185: :elixir_map."-assert_struct_keys/5-lc$^0/1-0-"/5
    (elixir) src/elixir_map.erl:62: :elixir_map.translate_struct/4
    (stdlib) lists.erl:1353: :lists.mapfoldl/3

[johnhamelink]

Some information @mitchellhenke and I have gathered over Slack:

• Changes to %Ecto.Changeset{} between 1.x and 2.x
• Ecto changelog
• Issue seems to be associated with parsing the field, not the schema, although due to macros, the stacktrace doesn't make this clear.
• Using IO.puts(Macro.to_string(macro)), we can debug the generated code produced by the macros.

[vic]

Hey, thanks for your work on getting this working with ecto 2.

I've created a new branch ecto-2.x and released a new version

I'll merge on master as soon as ecto 2 gets out of beta.

[johnhamelink]

@vic you are a beautiful human being 😄 Thanks for putting this out so quickly!