fix(check): env check false positive when value is defined but null #58
Conversation
This file contains 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
superbiche
force-pushed
the
fix/env-check-nullable-values
branch
from
c0ef6ab to
e22e0d6
Compare
|
@superbiche nice one, lgtm |
|
@superbiche that's been tagged at v1.12.2 |
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.
UKFast\HealthCheck\Checks\EnvHealthCheckcreates false positives when an environment value is set but its value isnull.This happens because
if (env($env) === null)returnstruefornullvalues, asenv('MISSING_KEY')returnsnull.Passing a (configurable) default value to
env()makes it easy to check if the default value was returned (which is what we really want).