Add support for umbrella projects #23
Open
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
After running mix deps.get, mix.lock was updated automatically.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation
When working with an umbrella project and performing
Envy.reload_config/0we got an exception because umbrella projects define their configuration at the root path instead of hardcodedconfig/config.exs.Proposed Solution
Relies on
Mix.Project.config/0to fetch project metadata and access:config_path. This key is always present even if it is not defined inmix.exs, so it will work on both Elixir applications (umbrella or standalone).Additional details
mix deps.get,mix.lockwas updated automatically.Envy.reload_config/0?