feat: update to Phoenix HTML 4.1, bump dependencies

[JakobLichterfeld]

No description provided.

[netlify]

✅ Deploy Preview for teslamate ready!

Name	Link
🔨 Latest commit	30a947a
🔍 Latest deploy log	https://app.netlify.com/sites/teslamate/deploys/67168198c8fe580008486cf7
😎 Deploy Preview	https://deploy-preview-4277--teslamate.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[JakobLichterfeld]

Thanks @sdwalker for your changes!

[brianmay]

Tests failing?

[JakobLichterfeld]

Tests failing?

Yeah, I assume this is the cause:

warning: defining a Gettext backend by calling

    use Gettext, otp_app: ...

is deprecated. To define a backend, call:

    use Gettext.Backend, otp_app: :my_app

Then, instead of importing your backend, call this in your module:

    use Gettext, backend: MyApp.Gettext

  lib/teslamate_web/gettext.ex:23: TeslaMateWeb.Gettext (module)

[sdwalker]

The mix files need cleaned to only have the phoenix changes and not include the rest of the unrelated package updates

The gettext warnings are simple fixes when updating gettext

The dependencies that aren't keeping up with package releases (websockex, timex) are another source of warnings
Bulma can be updated to 1.0.2 if you ignore the slew of deprecation warnings but their devs are keeping up

[JakobLichterfeld]

Yeah, I assume this is the cause:

warning: defining a Gettext backend by calling

    use Gettext, otp_app: ...

is deprecated. To define a backend, call:

    use Gettext.Backend, otp_app: :my_app

Then, instead of importing your backend, call this in your module:

    use Gettext, backend: MyApp.Gettext

  lib/teslamate_web/gettext.ex:23: TeslaMateWeb.Gettext (module)

I fixed it with the help of https://www.yellowduck.be/posts/fixing-the-gettext-warning-in-phoenix

[brianmay]

It looks like this function call

teslamate/test/teslamate/vault_test.exs

Line 11 in 30a947a

|> Cloak.Vault.read_config()

is returning a tuple, and we do not expect a tuple.

This puzzles me though, I don't see any changes here.

Oh, I think this change upgraded Clock, so we got this breaking change: danielberkompas/cloak@267077e.

Which is typical fashion wasn't documented as a breaking change :-(

https://github.com/danielberkompas/cloak/blob/master/CHANGELOG.md

[brianmay]

If I am reading the stack trace correctly, this is returning an error tuple:

teslamate/lib/teslamate/locations.ex

Line 58 in 30a947a

{:ok, attrs} = @geocoder.details(addresses, lang)

Which seems to indicate we are getting here somehow:

teslamate/test/support/mocks/geocoder.ex

Line 150 in 2fc749c

throw({:error, :boom})

[sdwalker]

Yeah, I assume this is the cause:

warning: defining a Gettext backend by calling

    use Gettext, otp_app: ...

is deprecated. To define a backend, call:

    use Gettext.Backend, otp_app: :my_app

Then, instead of importing your backend, call this in your module:

    use Gettext, backend: MyApp.Gettext

  lib/teslamate_web/gettext.ex:23: TeslaMateWeb.Gettext (module)

I fixed it with the help of https://www.yellowduck.be/posts/fixing-the-gettext-warning-in-phoenix

They match the local changes I've been using