Skip to content
This repository was archived by the owner on Jun 28, 2022. It is now read-only.

Config merging errors when default values is present #16

Closed
arantespp opened this issue Feb 8, 2021 · 0 comments · Fixed by #21
Closed

Config merging errors when default values is present #16

arantespp opened this issue Feb 8, 2021 · 0 comments · Fixed by #21

Comments

@arantespp
Copy link
Member

Currently, if we have a default value from options, environment options aren't taking into account.
@arantespp arantespp changed the title Config merging don't take into account default values Config merging doesn't take into account default values Feb 8, 2021
@arantespp arantespp changed the title Config merging doesn't take into account default values Config merging errors when default values is present Feb 9, 2021
arantespp added a commit that referenced this issue Feb 9, 2021
@arantespp
fix: fixes #16, fixes #17
429b806
@arantespp arantespp linked a pull request Feb 11, 2021 that will close this issue
feat: static app improvements and docs #21
Merged
arantespp added a commit that referenced this issue Feb 11, 2021
@arantespp
feat: static app improvements and docs (#21)
5723688 
* fix: fixes #16, fixes #17

* fix: fixes #18, fixes #19

* fix: fixes #20

* feat: improvements and docs
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: static app improvements and docs ttoss/carlin
1 participant
@arantespp