Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add defensive checks for edge cases #328

Merged
merged 2 commits into from
Oct 12, 2023
Merged

Conversation

arunshenoy99
Copy link
Member

  1. When the GET settings API cannot read the corrupted wpseo_social option and fails, it tends to return a failed API response. We then attempt to read this false value in React, causing a white screen.
  2. Point 1 leads to a false value being reported to the POST API, triggering an error in the debug log. While this doesn't result in a white screen, as a best practice, we have added a check anyway.

Both of these issues are incredibly rare but were prioritized for resolution. They are also challenging to replicate because of the rare nature.

Copy link
Contributor

@diwanshuster diwanshuster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@arunshenoy99 arunshenoy99 merged commit 51047f4 into trunk Oct 12, 2023
3 checks passed
@arunshenoy99 arunshenoy99 deleted the hotfix/edge-case-basic-info branch October 12, 2023 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants