Skip to content
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

Fix deprecation warnings in Elixir 1.11 #59

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hoyon
Copy link
Contributor

@hoyon hoyon commented Oct 16, 2020

Fix the following warnings when compiling with Elixir 1.11:

warning: Ecto.Query.exclude/2 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query]] to your "def project" in mix.exs

Found at 3 locations:
  lib/kerosene.ex:71: Kerosene.get_total_count/3
  lib/kerosene.ex:72: Kerosene.get_total_count/3
  lib/kerosene.ex:85: Kerosene.total_count/1

warning: Ecto.Query.limit/2 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query]] to your "def project" in mix.exs

  lib/kerosene.ex:49: Kerosene.get_items/4

warning: Ecto.Query.offset/2 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query]] to your "def project" in mix.exs

  lib/kerosene.ex:50: Kerosene.get_items/4

warning: Ecto.Query.select/2 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query]] to your "def project" in mix.exs

  lib/kerosene.ex:92: Kerosene.total_row_count/1

warning: Ecto.Query.select/3 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query]] to your "def project" in mix.exs

  lib/kerosene.ex:86: Kerosene.total_count/1

warning: Ecto.Query.subquery/1 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query]] to your "def project" in mix.exs

  lib/kerosene.ex:91: Kerosene.total_row_count/1

warning: Ecto.Query.Builder.field!/1 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query.Builder]] to your "def project" in mix.exs

  lib/kerosene.ex:86: Kerosene.total_count/1

warning: Ecto.Query.Builder.LimitOffset.apply/3 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query.Builder.LimitOffset]] to your "def project" in mix.exs

  lib/kerosene.ex:50: Kerosene.get_items/4

warning: Ecto.Query.Builder.Select.apply/2 defined in application :ecto is used by the current application but the current application does not directly depend on :ecto. To fix this, you must do one of:

  1. If :ecto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :ecto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :ecto, you may optionally skip this warning by adding [xref: [exclude: Ecto.Query.Builder.Select]] to your "def project" in mix.exs

Found at 2 locations:
  lib/kerosene.ex:86: Kerosene.total_count/1
  lib/kerosene.ex:92: Kerosene.total_row_count/1

warning: Phoenix.HTML.__using__/1 defined in application :phoenix_html is used by the current application but the current application does not directly depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: Phoenix.HTML]] to your "def project" in mix.exs

Found at 9 locations:
  lib/kerosene/html.ex:2: Kerosene.HTML
  lib/kerosene/html/bootstrap.ex:4: Kerosene.HTML.Bootstrap
  lib/kerosene/html/bootstrap4.ex:4: Kerosene.HTML.Bootstrap4
  lib/kerosene/html/foundation.ex:4: Kerosene.HTML.Foundation
  lib/kerosene/html/materialize.ex:4: Kerosene.HTML.Materialize
  lib/kerosene/html/semantic.ex:4: Kerosene.HTML.Semantic
  lib/kerosene/html/simple.ex:3: Kerosene.HTML.Simple
  lib/kerosene/json.ex:2: Kerosene.JSON
  lib/kerosene/paginator.ex:2: Kerosene.Paginator

warning: Phoenix.HTML.Link.link/2 defined in application :phoenix_html is used by the current application but the current application does not directly depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: Phoenix.HTML.Link]] to your "def project" in mix.exs

Found at 6 locations:
  lib/kerosene/html/bootstrap.ex:11: Kerosene.HTML.Bootstrap.generate_links/2
  lib/kerosene/html/bootstrap4.ex:11: Kerosene.HTML.Bootstrap4.generate_links/2
  lib/kerosene/html/foundation.ex:10: Kerosene.HTML.Foundation.generate_links/2
  lib/kerosene/html/materialize.ex:10: Kerosene.HTML.Materialize.generate_links/2
  lib/kerosene/html/semantic.ex:9: Kerosene.HTML.Semantic.generate_links/2
  lib/kerosene/html/simple.ex:8: Kerosene.HTML.Simple.generate_links/2

warning: Phoenix.HTML.Tag.content_tag/2 defined in application :phoenix_html is used by the current application but the current application does not directly depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: Phoenix.HTML.Tag]] to your "def project" in mix.exs

Found at 2 locations:
  lib/kerosene/html/bootstrap.ex:7: Kerosene.HTML.Bootstrap.generate_links/2
  lib/kerosene/html/bootstrap4.ex:7: Kerosene.HTML.Bootstrap4.generate_links/2

warning: Phoenix.HTML.Tag.content_tag/3 defined in application :phoenix_html is used by the current application but the current application does not directly depend on :phoenix_html. To fix this, you must do one of:

  1. If :phoenix_html is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :phoenix_html is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :phoenix_html, you may optionally skip this warning by adding [xref: [exclude: Phoenix.HTML.Tag]] to your "def project" in mix.exs

Found at 10 locations:
  lib/kerosene/html/bootstrap.ex:8: Kerosene.HTML.Bootstrap.generate_links/2
  lib/kerosene/html/bootstrap.ex:10: Kerosene.HTML.Bootstrap.generate_links/2
  lib/kerosene/html/bootstrap4.ex:8: Kerosene.HTML.Bootstrap4.generate_links/2
  lib/kerosene/html/bootstrap4.ex:10: Kerosene.HTML.Bootstrap4.generate_links/2
  lib/kerosene/html/foundation.ex:7: Kerosene.HTML.Foundation.generate_links/2
  lib/kerosene/html/foundation.ex:9: Kerosene.HTML.Foundation.generate_links/2
  lib/kerosene/html/materialize.ex:7: Kerosene.HTML.Materialize.generate_links/2
  lib/kerosene/html/materialize.ex:9: Kerosene.HTML.Materialize.generate_links/2
  lib/kerosene/html/semantic.ex:7: Kerosene.HTML.Semantic.generate_links/2
  lib/kerosene/html/simple.ex:6: Kerosene.HTML.Simple.generate_links/2

warning: Plug.Conn.Query.encode/1 defined in application :plug is used by the current application but the current application does not directly depend on :plug. To fix this, you must do one of:

  1. If :plug is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :plug is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :plug, you may optionally skip this warning by adding [xref: [exclude: Plug.Conn.Query]] to your "def project" in mix.exs

  lib/kerosene/paginator.ex:87: Kerosene.Paginator.build_query/1

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.

1 participant