-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Why not use environment variables available through Schema's #67
Comments
Yes, it's definitely a downside to add more logic for different environment URLs. Having said that, which paragraph are you referring to? |
As mentioned in the readme about constants, we are typically hardcoding the API URL into the application.
There are many times the app needs to run with staging, development and production environment API's and each of them may have different urls. Hard coding them in constants seems to add more logic to check the current environment and then act upon it.
With multiple schemas with their own environment variables solves the problem.
The text was updated successfully, but these errors were encountered: