Minor improvements in code complexity with early returns and early validation #116
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.
Hi there,
I noticed a few minor improvements that we could make in the
Guard
class.Guard::__construct
has a call that it initializes$this->keyPair = null
. This can be moved to the property declaration without changing the functionality.$strength < 16
check, which can be moved to the top as well, so the later calls are not executed if we have to throw an exception. The early calls do not mutate state.Guard::validateToken()
andGuard::enforceStorageLimit()
methods have nestedif
calls, which can be removed in favor of early returns.Fingers crossed this can be merged, and I'm open to make any further changes if necessary. Thank you for your time.