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.
What will it allow you to do that you can't do today?
beacon_live_admin retains the same functionality, but a potential blocker for releases is removed.
Why do you need this feature and how will it benefit other users?
While building a release of an umbrella application featuring beacon in one of the child apps and beacon_live_admin in another, I was running into a
MatchError
that was preventing the release from being started:By making this small edit, I enabled my release to start successfully.
Are there any drawbacks to this feature?
Not that I can tell. All of beacon_live_admin’s tests still run without failures. The umbrella application still runs successfully with
mix phx.server
. And the release is able to start without any issues.