In order to wrap the Desk Tool in a <Provider> element, I'm removing @sanity/desk-tool from the main list of plugins, and replacing it with localized, which exports a DeskTool wrapped in a provider.

When I start sanity, I get errors along the lines of:

Error in ./node_modules/@sanity/desk-tool/lib/pane/EditorPane.jsModule not found: Error: Part "part:@sanity/form-builder" not implemented by any plugins
 @ ./node_modules/@sanity/desk-tool/lib/pane/EditorPane.js 26:19-55
 @ ./node_modules/@sanity/desk-tool/lib/pane/Pane.js
 @ ./node_modules/@sanity/desk-tool/lib/DeskToolPanes.js
 @ ./node_modules/@sanity/desk-tool/lib/DeskTool.js
 @ ./node_modules/@sanity/desk-tool/lib/index.js
 @ ./plugins/localized/index.js
 @ ./plugins/localized (all:part:@sanity/base/tool)
 @ ./node_modules/@sanity/default-layout/lib/defaultLayoutRouter.js
 @ ./node_modules/@sanity/default-layout/lib/components/DefaultLayoutContainer.js (part:@sanity/base/root)
 @ ./node_modules/@sanity/base/lib/components/SanityRoot.js (part:@sanity/base/sanity-root)
 @ ./node_modules/@sanity/server/lib/browser/entry-dev.js
 @ multi ./node_modules/react-hot-loader/patch.js ./node_modules/normalize.css/normalize.css ./node_modules/@sanity/server/lib/browser/entry-dev.js

I discovered (by mistake) that if I start sanity with the default @sanity/desk-tool plugin, let it compile, and then replace it with localized, everything works as expected.

To recreate this:

• run npm run start. You'll see the errors.
• Cancel it, swap the keys of _plugins and plugins in sanity.json, then npm run start again.
• While still running, swap the keys back to use localized.

Questions:

• Is there an easier way to wrap everything in a provider?
• Or, if exporting a wrapped DeskTool within the plugin (as I am doing) is the best approach, what's up with these errors and how can I get it going?

The function localizeField (see here) takes a standard field config and "localizes" it. (See it in use in the post schema)

usage:

	fields: [
		localizeField({
			name: 'title',
			title: 'Title',
			type: 'string',
		}),
		...
	]

It turns this field into an object with translations for each language. The above example turns into:

	fields: [
		{
			name: 'title',
			title: 'Title',
			type: 'object',
			fields: [
				{
					name: 'en',
					title: 'English',
					type: 'string',
				},
				{
					name: 'es',
					title: 'Spanish',
					type: 'string',
				},
				// ... and so on for other languages
			]
		}
		...
	]

This is done by copying the implementation of the core ObjectInput component, with the only difference being that it hides the input if it is not the current language.

As you can see in the function, it is literally just copied and pasted.

Question

Is there an easier way to render the child fields without needing to re-implement handleFieldChange and all of the other props?