fix: getCurrentEntryId() should return null instead of false #5416
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.
WHY
BEFORE - What was wrong? What was happening before this PR?
getCurrentEntryId()
returns false, but ideally it should be returning null if unable to retrieve a value.There are also several places in the codebase that use this line to get the crud ID:
A few files:
src/app/Http/Controllers/Operations/DeleteOperation.php
src/app/Http/Controllers/Operations/ListOperation.php
src/app/Http/Controllers/Operations/ShowOperation.php
src/app/Http/Controllers/Operations/UpdateOperation.php
This will never allow you to fallback to
$id
using null coalescing since it returns false and doesn't return null.AFTER - What is happening after this PR?
change the return type from false to null, so that we can make use of fallbacks via null coalescing
HOW
How did you achieve that, in technical terms?
update the return type from false -> null
Is it a breaking change?
potentially if people are strictly checking for
FALSE
but if looselynull
is falsy so should be fineHow can we test the before & after?
??
If the PR has changes in multiple repos please provide the command to checkout all branches, eg.: