forked from ianstormtaylor/slate
-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathwith-react.ts
More file actions
78 lines (66 loc) · 2.59 KB
/
with-react.ts
File metadata and controls
78 lines (66 loc) · 2.59 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
import ReactDOM from 'react-dom'
import { type BaseEditor, Node } from 'slate'
import { EDITOR_TO_PENDING_SELECTION, IS_ANDROID, withDOM } from 'slate-dom'
import { getChunkTreeForNode } from '../chunking'
import { REACT_MAJOR_VERSION } from '../utils/environment'
import { ReactEditor } from './react-editor'
/**
* `withReact` adds React and DOM specific behaviors to the editor.
*
* If you are using TypeScript, you must extend Slate's CustomTypes to use
* this plugin.
*
* See https://docs.slatejs.org/concepts/11-typescript to learn how.
*/
export const withReact = <T extends BaseEditor>(
editor: T,
clipboardFormatKey = 'x-slate-fragment'
): T & ReactEditor => {
let e = editor as T & ReactEditor
e = withDOM(e, clipboardFormatKey)
const { onChange, apply, insertText } = e
e.getChunkSize = () => null
if (IS_ANDROID) {
e.insertText = (text, options) => {
// COMPAT: Android devices, specifically Samsung devices, experience cursor jumping.
// This issue occurs when the insertText function is called immediately after typing.
// The problem arises because typing schedules a selection change.
// However, this selection change is only executed after the insertText function.
// As a result, the already obsolete selection is applied, leading to incorrect
// final cursor position.
EDITOR_TO_PENDING_SELECTION.delete(e)
return insertText(text, options)
}
}
e.onChange = (options) => {
// COMPAT: React < 18 doesn't batch `setState` hook calls, which means
// that the children and selection can get out of sync for one render
// pass. So we have to use this unstable API to ensure it batches them.
// (2019/12/03)
// https://github.com/facebook/react/issues/14259#issuecomment-439702367
const maybeBatchUpdates =
REACT_MAJOR_VERSION < 18
? ReactDOM.unstable_batchedUpdates
: (callback: () => void) => callback()
maybeBatchUpdates(() => {
onChange(options)
})
}
// On move_node, if the chunking optimization is enabled for the parent of the
// node being moved, add the moved node to the movedNodeKeys set of the
// parent's chunk tree.
e.apply = (operation) => {
if (operation.type === 'move_node') {
const parent = Node.parent(e, operation.path)
const chunking = !!e.getChunkSize(parent)
if (chunking) {
const node = Node.get(e, operation.path)
const chunkTree = getChunkTreeForNode(e, parent)
const key = ReactEditor.findKey(e, node)
chunkTree.movedNodeKeys.add(key)
}
}
apply(operation)
}
return e
}