Skip to content

Update to Ecto 3.0 and remove timex_ecto. This fixes #394 - #398

Open
johannesE wants to merge 2 commits into
smpallen99:masterfrom
johannesE:#394
Open

Update to Ecto 3.0 and remove timex_ecto. This fixes #394#398
johannesE wants to merge 2 commits into
smpallen99:masterfrom
johannesE:#394

Conversation

@johannesE

Copy link
Copy Markdown

This might be completely stupid. But I didn't find any usage of Timex.Ecto.* anywhere in the code and the Tests are still green.

Cast only accepts atoms in the future, so I made sure we were only using those.
Applications should not be defined. This would lead to errors otherwise.
migrations_path is now Ecto.Migrator.migrations_path
@johannesE

johannesE commented Nov 17, 2018

Copy link
Copy Markdown
Author

I also upgraded to Ecto 3.0. to fully fix #394. I fixed the resulting warnings and errors.

@johannesE johannesE changed the title Try to fix #394 by simply removing the timex_ecto dependency Update to Ecto 3.0 and remove timex_ecto. This fixes #394 Nov 17, 2018
@mikehostetler

Copy link
Copy Markdown

You can easily include this version of coherence into your app by adding the following to your mix.exs file:

{:coherence, git: "https://github.com/johannesE/coherence", branch: "#394"},

@johannesE

Copy link
Copy Markdown
Author

You can easily include this version of coherence into your app by adding the following to your mix.exs file:

{:coherence, git: "https://github.com/johannesE/coherence", branch: "#394"},

While that is true, I do not plan to become the new maintainer for coherence ;-).

Maybe someone could review this? @smpallen99

@augnustin

Copy link
Copy Markdown

I do not plan to become the new maintainer for coherence

You're on dude! Thanks 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants