Increase getSchemaRequested/getSchemaResponse to public methods

[robbieaverill]

Controllers that want to use the new React form builder style APIs can use LeftAndMain::getSchemaRequested and ::getSchemaResponse to help with the client app communication.

Extensions to LeftAndMain controllers can't though because they're protected methods.

As a result, you see examples like this happening instead.

At this stage I can only see asset-admin will be affected by this in core packages.

Related issues

• Remove duplicated methods (getSchemaRequested() and getSchemaResponse()) silverstripe-contentreview#214

[chillu]

What use case needs Extension rather than extending a base controller? I can see the need in ModalController, but what else is this blocking at the moment?

[robbieaverill]

So the use case I have at the moment is content review, which adds some functionality to CMSPageEditController via a LeftAndMainExtension.

I suppose that two immediate possibilities that don't involve changing the visibility in LeftAndMain could be to increase the visibility in the LeftAndMainExtension instead, or to use entirely separate controllers instead of extending the CMS controller.

[tractorcow]

I'd rather move it out of LeftAndMain altogether. What about putting it in FormSchema?

[tractorcow]

getSchemaRequested is 2 lines; I'm not worried so much if someone has to inline this somewhere.

[tractorcow]

This logic needs to be shifted out of LeftAndMain, and I would prefer to put it into LeftAndMainFormRequestHandler which is where all form-schema response handling should be done.

The forms themselves are the natural delegates for handling their own schema.