[12.x] Update assertSessionMissing()
signature to match assertSessionHas()
#55763
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.
Problem
Until now, it has been impossible to check the session to confirm that a specific value is not set.
For example: let's say I have a session key called
guest_id
which contains a value that must rotate to a new randomly generated string on every page view. Prior to this patch, there was no easy way to validate that the value had actually changed. You could assert that the key was the same or that the value was missing, but you could not check that it had rotated to some new unknown value.NOTE: This is not a breaking change
Proposed solution
I mostly replicated the logic from
assertSessionHas()
above to allow a user to provide a specific value that must not be set in a specific key. Also likeassertSessionHas()
, it preserves the original logic where if no value is provided, it just checks that the key is missing altogether.