Spike/version beta components

[andy-little]

A demo of how we might organise versioned components in the future (starting with beta components)

[andy-little]

We’ll need some metadata, but I’m not sure this is quite right yet. My thinking behind pre-release is that it lets us merge work into spark without exposing the component in the insert menu, since it may not be implemented elsewhere in the content pipeline yet.

Deprecated might not be needed. It may be enough to say that once a newer version is supported, earlier versions are implicitly deprecated.

[andy-little]

This doesn't work as I hoped. I was envisaging a schema with something like:

"ContentTree.transit.AudioPlayer {
            "anyOf": [
               {
                    "$ref": "#/definitions/ContentTree.transit.AudioPlayerV1"
                },
                {
                    "$ref": "#/definitions/ContentTree.transit.AudioPlayerV2"
                },
                {
                    "$ref": "#/definitions/ContentTree.transit.AudioPlayerV3"
                }
            ]

But we end up flattening the union on bodyblock... which makes sense 🤔.

I think we can probably still work with this using the type property as a stable name