API Fetch: Fix error on empty OPTIONS preload data #14714
Merged
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.
Previously: #4155 (cc @imath)
This pull request seeks to resolve an error which occurs when the API Fetch preloading middleware is initialized with an empty object. Notably, this impacts preload request tests against
OPTIONS
requests, which prior to these changes performed an unsafe object property access.Testing instructions:
Ensure unit tests pass:
Verify that no errors occur when resetting preloaded data to an empty array, placing the following snippet in some PHP code (e.g. a custom mu-plugin or
gutenberg/gutenberg.php
).