Update Blueprint schema to remove alerts when using the shorthand syntax

[ironnysh]

When using VS Code to compose a Blueprint that contains the shorthand syntax of the siteOptions step and plugins step, the editor alerts that these are deprecated:

Now that shorthands are here to stay and featured in the official docs, it's probably safe to remove the warnings from the schema (see these lines).

BTW, the Builder doesn't identify the shorthand syntax as an error. Is it using another version of the schema for validation?

[bph]

Hmm, the deprecation message reads: 'This experimental option will change without warning.\nUse steps instead."

That's making it a bit clearer, that it's experimental and not obsolete.
Are shorthand blueprint properties to stay?
Is there a way for VS Code to display that message?

The JSON schema specs notice the deprecated property needs to be boolean.

"The value of this keyword MUST be a boolean. When multiple occurrences of this keyword are applicable to a single sub-instance, applications SHOULD consider the instance location to be deprecated if any occurrence specifies a true value.

If "deprecated" has a value of boolean true, it indicates that applications SHOULD refrain from usage of the declared property. It MAY mean the property is going to be removed in the future."

[bph]

@adamziel let me know if the implementation is cemented enough for the "deprecated" property to be removed, and I create a PR for it.

[ironnysh]

Here's the original discussion (for reference/background):

... are the shorthands documented somewhere?

They aren't at the moment, I've added them as an experimental feature a few months ago and didn't want to spread them too much in case I'd have to remove them later on. Today I'm quite certain they're here to stay which also means there are no more blockers to documenting them.

[bph]

The documentation is available: https://wordpress.github.io/wordpress-playground/blueprints-api/steps-shorthands

[ironnysh]

Yup, I did it based on @adamziel's explanation 😊

[bph]

Thank you @ironnysh. Wonderful.

[bgrgicak]

The siteOptions step and plugins aren't marked as deprecated anymore, so I'm going to close this issue.

Thank you @bph and @ironnysh!

[adamziel]

I think lack of deprecation info was just a documentation quirk, the "deprecated" property was still there in JSON schema. I started #1594 to remove it.