✨ Increased transparency by always using env var names #55
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rvfch
force-pushed
the
feat/96040-env-var-names
branch
3 times, most recently
from
8bddb7e to
efa9722
Compare
pavelsvagr
force-pushed
the
feat/96040-env-var-names
branch
3 times, most recently
from
a625585 to
8a6ef11
Compare
pavelsvagr
force-pushed
the
feat/96040-env-var-names
branch
4 times, most recently
from
49904c4 to
72705f4
Compare
pavelsvagr
force-pushed
the
feat/96040-env-var-names
branch
2 times, most recently
from
400e880 to
6fdd21c
Compare
Member
|
Things to consider - Change of the API and using recursive object traversal should be okay for config files, but it also increases complexity of the library. For example checking nested fields is now done on the whole object if the function is |
smoliji
requested changes
Jan 8, 2026
wiki/advanced-usage.md
Outdated
Comment on lines
38
to
67
| ### Reloading the config | ||
|
|
||
| If you are working in an environment that is able to change the configuration during runtime, `reload` | ||
| function can be helpful to load a new configuration based on same settings and schema as the previous one. | ||
|
|
||
| ```typescript | ||
| import { createLoader, schema } from 'configuru' | ||
| const loader = createLoader() | ||
|
|
||
| const configSchema = loader({ | ||
| canChange: schema.string('CHANGEABLE'), | ||
| }) | ||
|
|
||
| const { canChange } = configSchema.values() // old value | ||
|
|
||
| // value changed in config file or env variables during runtime | ||
|
|
||
| const { canChange } = configSchema.reload().values() // new value |
Contributor
There was a problem hiding this comment.
nitpick: Super cool feature to keep the config up to date, however nothing to do with the original issue #52, different PR for such a huge feat. would make more sense.
pavelsvagr
force-pushed
the
feat/96040-env-var-names
branch
4 times, most recently
from
cba5026 to
a1fd713
Compare
pavelsvagr
force-pushed
the
feat/96040-env-var-names
branch
from
a1fd713 to
e619222
Compare
smoliji
approved these changes
Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR addresses:
SERVER_PORT: schema.string()reloadfunction for automatic config reload based on previous settingsNew example usage viz docs.
Fixes #52
REDMIME-96040