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

Feature: Unify the API for config vars #1325

Open
a-alhusaini opened this issue Jun 27, 2023 · 1 comment
Open

Feature: Unify the API for config vars #1325

a-alhusaini opened this issue Jun 27, 2023 · 1 comment

Comments

@a-alhusaini
Copy link

a-alhusaini commented Jun 27, 2023

Original Message Deleted

It turned out that this feature was already implemented in Amber. But no one documented it.

You can override values defined inside .yml files in the config/settings.cr file. It essentially acheives the goals of this issue: Which is to provide a clean API for accessing configuration variables.

TODO: Document this feature.

@crimson-knight
Copy link
Member

I like this.

Right now I can say that if there is an ENV declared that does exist in one of the environment yaml files, Amber will prefer the ENV declaration over the yaml file version.

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

No branches or pull requests

2 participants