Give context in no-widget-for-type exception

[quazgar]

Prerequisites

• I have read the documentation

What theme are you using?

core

Is your feature request related to a problem? Please describe.

When no widget for a given specification can be found, the error message does not mention where the error occurs, although the context is available to the code.

Example playground link: Array with "ui:widget": "radio"

Describe the solution you'd like

The error should mention where in the schema the problem occurs.

The call stack for specific error looks like this:

getWidget(): getWidget.js: 114
renderCustomWidget(): ArrayField.js: 444
render(): ArrayField.js: 369

In render() in ArrayField.js, all the necessary information for a more meaningful Error message is available: schema and idSchema give the context which developers can use to pinpoint the problem (an invalid widget specification in this case).

Describe alternatives you've considered

Setting a breakpoint at getWidget.js:114 can also be used, but only if the problem is reproducible for developers. Users reporting the error typically don't have this possibility.

[heath-freenome]

@quazgar I agree that if we printed out the schema that was passed to getWidget() then it would definitely help. Adding the idSchema would require a breaking change to the getWidget() function which I am hesitant to do. I know that my own company uses getWidget() alot. Thoughts?

[quazgar]

The error could be caught here in renderCustomWidget(), where the information is available, without changing the function's signature.

[heath-freenome]

@quazgar That's only one location where getWidget() is used. Also, I did update getWidget() to output the schema in the errors

[heath-freenome]

@quazgar Was the update I provided to add the schema to the error output sufficient?

[quazgar]

I would say, it is much better already, although the context would cover more cases than the inner schema. For example in this playground, if the element did not have the title set (or if it was ambiguous), the user would still not know where the error happens.