@sanalabs/y-redux v0.1.13

@sanalabs/y-redux

This package exports two React components:

• SyncYJson: Two-way synchronization of a deep YMap/YArray and a Redux state.
• SyncYAwareness: Synchronization of YDoc awareness states (remote and local) and a Redux state.

Table of Contents

• SyncYJson
  • Retaining referential equality whenever possible
  • Usage example
• SyncYAwareness
• FAQ
  • Why is SyncYJson a component and not a hook?
  • Why is SyncYJson a React component and not a more generic Redux integration?

SyncYJson

This is a two-way synchronization of a Redux state and a YMap/YArray. When SyncYJson is mounted it keeps the state in sync by:

1. Listening for changes to the YType (observeDeep) and writing them to the Redux state (dispatching an action).
2. Listening for changes to the Redux state (useSelector) and writing them to the YType (Yjs mutation operations).

The YType can be a deep structure containing YMaps, YArrays and JSON primitives.

The Yjs mutations are batched into a transaction.

Retaining referential equality whenever possible

Retaining object references for parts of the state that didn't change is important for performance and allows the caching mechanism of Redux selectors to function correctly.

• Redux to Yjs: SyncYJson uses patchYJson which creates Yjs operations only for the part of the state that changed.
• Yjs to Redux: This can be done by using deepPatchJson (exported from @sanalabs/json) in the reducer that applies the Redux updates. See example (TODO).

Usage example

export const App = () => {
  const { yMap, yProvider } = useMemo(() => {
    const yProvider = new YjsProvider() // Eg. HocuspocusProvider or WebrtcProvider
    const yMap = yProvider.document.getMap('data')
    return { yMap, yProvider }
  }, [])

  useEffect(
    () => () => {
      yProvider.destroy()
    },
    [yProvider]
  )

  return (
    <SyncYJson
      yMap={yMap} // YMap to be observed for remote changes by yMap.observeDeep
      setData={setData} // Action creator to be called as dispatch(setData(data))
      selectData={selectData} // Selector to be used as useSelector(selectData)
    />

    // Inside other components you can interact with the synced data as with any normal
    // Redux state by using dispatch and useSelector and it will be seamlessly kept in sync.
    <OtherComponent />
  )
}

SyncYAwareness

Very similar to SyncYJson

FAQ

Why is SyncYJson a component and not a hook?

For performance and convenience. It makes no difference to the consumer of this API since SyncYJson doesn't return anything. Think of the component as a provider component.

The performance issue with hooks is that any time an effect within a hook runs, that triggers a re-render of the surrounding component. Since the hooks within SyncYJson may trigger very often due to remote changes we noticed that it was not convenient to have the functionality as a hook.

Why is SyncYJson a React component and not a more generic Redux integration?

Having this logic as a first class citizen in React makes it easy to control when to use SyncYJson and to have multiple instances for different parts of your application.