Update Global Styles endpoint to support non-experimental paths #15002
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.
This updates the Global styles endpoint to use the non-experimental paths for fetching the block editor settings.
📓 Note that the Jetpack side is still dependent on some backend changes so this PR is still a draft.
WordPress-FluxC-AndroidPR: wordpress-mobile/WordPress-FluxC-Android#2049To test:
For each of these cases, it'll be enough to open the editor and validate that the correct color options are available. It would also be useful to test using a network monitoring tool to make sure the correct paths are called. This will help ensure you aren't seeing cached data if you're reusing the same site for testing.
__experimental/wp-block-editor/v1/wp-block-editor/v1__experimental/wp-block-editor/v1/wp-block-editor/v1Regression Notes
Potential unintended areas of impact
N/A
What I did to test those areas of impact (or what existing automated tests I relied on)
N/A
What automated tests I added (or what prevented me from doing so)
Check
WordPress-FluxC-AndroidPRPR submission checklist:
RELEASE-NOTES.txtif necessary.