clients/client/elixir refers to an unavailable application
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 178
- Forks
- 96
- Avg merge
- 6d 23h
- Merged PRs (30d)
- 3
Description
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Cloud project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe the bug
When compiling clients/client/elixir, the following message is printed:
You have configured application :ory_apis in your configuration file,
but the application is not available.
This usually means one of:
1. You have not added the application as a dependency in a mix.exs file.
2. You are configuring an application that does not really exist.
Please ensure :ory_apis exists or remove the configuration.
The documentation also refers to this:
## Configuration
You can override the URL of your server (e.g. if you have a separate development and production
server in your configuration files.
config :ory_apis, base_url: "https://playground.projects.oryapis.com"
However, mix.exs calls the application :ory_client, which is the name that should be used in the configuration and examples.
I haven’t played with the code generation process, so I am not sure where :ory_apis vs :ory_client is coming from, but it is an issue.
Reproducing the bug
$ mix do deps.get, compile
Relevant log output
No response
Relevant configuration
No response
Version
n/a
On which operating system are you observing this issue?
No response
In which environment are you deploying?
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with clients/client/elixir/mix.exs and the configuration example shown in the issue, then run mix do deps.get, compile to reproduce the unavailable application warning. Trace where the application name is set in the Elixir client and its generated documentation. Done means the configured application name and examples match the application declared by mix.exs and compilation completes without this warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100