Performance lab playground integration Fixed

[iqbal-web]

Current blueprint not working. In this Pr, update it.

For Test: Playground Builder

Fixed #2279

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: iqbal-web <[email protected]>
Co-authored-by: westonruter <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[westonruter]

@iqbal-web Why does this fix the issue?

Here's Playground with the blueprint.json currently in the trunk branch:

https://playground.wordpress.net/?blueprint-url=https%3A%2F%2Fraw.githubusercontent.com%2FWordPress%2Fperformance%2Frefs%2Fheads%2Ftrunk%2Fplugins%2Fperformance-lab%2F.wordpress-org%2Fblueprints%2Fblueprint.json

You can see that it loads with Performance lab as expected.

The changes you've introduced here just remove slash escapes, which shouldn't impact the resulting parsed JSON in any way. That said, it would indeed be good to remove those slashes since they aren't needed.

When I load up blueprint.json I see some validation issues in PhpStorm:

I also see validation issues in JSON Schema Validator: https://www.jsonschemavalidator.net/s/smWcDkog

Perhaps this is why WordPress.org isn't showing the Preview button?

[iqbal-web]

Why does this fix the issue?

When exploring wordpress plugins, Gutenberg only has which live preview that is working. So I checked the blueprint JSON file here and found some inconsistencies. So I update it like Gutenberg's current use.

https://github.com/WordPress/gutenberg/blob/trunk/assets/blueprints/blueprint.json

When I load up blueprint.json I see some validation issues in PhpStorm:

Switch my pr, then run the validation. It will be fixed then.

@wordpress/prettier-config WordPress Prettier config enforces unescaped forward slashes

@westonruter