Skip to content

Add `:public_key` to `extra_applications`

minibikini requested to merge fix/public-key-warnings into master

Fixes compilation warnings:

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

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

  2. If :public_key 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 :public_key, you may optionally skip this warning by adding [xref: [exclude: :public_key]] to your "def project" in mix.exs

Found at 3 locations:
  test/support/test_adapter.ex:11: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:17: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:21: HTTPSignatures.TestAdapter

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

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

  2. If :public_key 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 :public_key, you may optionally skip this warning by adding [xref: [exclude: :public_key]] to your "def project" in mix.exs

Found at 3 locations:
  test/support/test_adapter.ex:15: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:18: HTTPSignatures.TestAdapter
  test/support/test_adapter.ex:23: HTTPSignatures.TestAdapter

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

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

  2. If :public_key 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 :public_key, you may optionally skip this warning by adding [xref: [exclude: :public_key]] to your "def project" in mix.exs

  lib/http_signatures/http_signatures.ex:87: HTTPSignatures.sign/3

warning: :public_key.verify/4 defined in application :public_key is used by the current application but the current application does not directly depend on :public_key. To fix this, you must do one of:

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

  2. If :public_key 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 :public_key, you may optionally skip this warning by adding [xref: [exclude: :public_key]] to your "def project" in mix.exs

  lib/http_signatures/http_signatures.ex:37: HTTPSignatures.validate/3

Merge request reports