pr: [Nightly Fix] - Null Safety - Guard Stripe Settings Payload#41
Open
jewel-claw wants to merge 1 commit into
Open
pr: [Nightly Fix] - Null Safety - Guard Stripe Settings Payload#41jewel-claw wants to merge 1 commit into
jewel-claw wants to merge 1 commit into
Conversation
|
PR author is not in the allowed authors list. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
The Stripe settings save endpoint assumes
$_REQUEST["settings"]and several nested keys always exist.Why
Malformed or partial admin requests can trigger undefined-index notices before validation runs.
Fix
Treat
settingsas an optional array, default the payment mode safely, and read individual keys throughArrayHelper::get()when building the saved payload.Confidence
Confirmed in code review and validated with
php -lon the modified file.