Add example on how to wrap and customize the block editor

[skogsmaskin]

A working example on how to wrap and customise inputs would be nice to have in the example studio right?

[bjoerge]

Remove the constructor?

[bjoerge]

I'm a bit sceptical to documenting this as the way to get the default block editor, as it makes refactoring the internals of the form-builder package a breaking change. IMO our official stance should be to never recommend importing anything from ./lib

[bjoerge]

Just realized that the BlockEditor is exported by default as SlateInput

sanity/packages/@sanity/form-builder/src/index.js

Line 12 in 54b0c22

export {default as SlateInput} from './inputs/BlockEditor-slate'

If we change the exported name to BlockEditor, the import would be:

import {BlockEditor} from '@sanity/form-builder'

[skogsmaskin]

That would be nice yes!

[bjoerge]

Renamed in #210

[skogsmaskin]

I just realized that @sanity/form-builder is not a direct dependency in the studio :(

[bjoerge]

Fixed in #210 by exporting it from the sanity form builder part

[bjoerge]

So the import would now be:

import {BlockEditor} from 'part:@sanity/form-builder'

[bjoerge]

If all handleChange do is just call the given onChange-prop, maybe just pass it from render()?

render() {
  const {type, value, level, onChange} = this.props
  return (
    //...
    <SlateEditor
      //...
      onChange={onChange}
     />
    //...
  )
}

[skogsmaskin]

I think it has some value to show that you can make your own handler and do stuff. As you say in the below comment (readable.io).

[bjoerge]

True, but then maybe we should add an example where we are actually doing something with the value (or at least a comment in handleChangedescribing that we could do something with the value if we wanted to)

[bjoerge]

This is nice! Possible future work could be to turn it into an example of how to use it with an external service like readable.io.

[bjoerge]

💖