Switch back to draft.js from slate.js, requesting some basic features.

Do you want to request a feature or report a bug? feature

1. A lot of people using draft.js just to render a resizable textarea in React(or at least to start with),But

• draft.js makes it really hard to render a textarea with predetermined text. yes, we have EditorState.createEmpty(), but how to create initial state with text? With some digging I find EditorState.createWithContent(ContentState.createFromText(text)), not obvious to new users.
• Also how to extract text from state? state.getCurrentContent().getPlainText()

When I’m switching back from slate.js(because some bug they are not actively fixing), here’s the comparison:

import { Editor, EditorState, ContentState } from 'draft-js'

const Plain = {
  deserialize: text =>
    EditorState.createWithContent(ContentState.createFromText(text)),

  serialize: state => state.getCurrentContent().getPlainText()
}

compare to import { Editor,Plain } from 'slate' Is there some way to trim it down to more user friendly api like in slate.js? Or at least inform us on the tutorial starting demo?

1. Also slate provide a method on <Editor/>, onDocumentChange when the actual content changes. I find it useful as onChange triggers way to often.

2. And they provide a className property(makes more sense to me), instead of having to create a wrapper div.

[bryanph]

@FateRiddle If I may ask, what made you move back? I was considering the switch due to the lack of mobile support in draft.js

[niveditc]

I don’t think we’ll be making major changes to the API at the moment.

• PRs to make the docs more beginner-friendly are always welcome.
• A method like onDocumentChange needs you to define what exactly a ‘document’ is. This means different things in different editor use cases. One of the power features of Draft, in my opinion, is the flexibility to customize the input to what you want. onChange allows you to do that by exposing all the changes and letting you address whichever ones you want.
• #1713 is open for adding an additional style prop. We’ll try to review that soon.
• #725 is the umbrella issue for the Android/mobile bugs mentioned here.

In view of this, I’m closing this issue. Let me know if you have further questions!