fix(core): derive onValueChange and onSelectionChange from onChange (#2700)

[Samarth1306w]

• Auto release

Description

Derives onValueChange and onSelectionChange directly inside the Slate onChange handler within useSlateProps.ts.

Problem Solved

Previously, onChange, onValueChange, and onSelectionChange were handled as independent callbacks. When Slate fired onChange, component subscribers to value or selection changes could miss updates or receive re-renders out of order.

Solution

Track prevValueRef and prevSelectionRef. Inside onChange:

1. Trigger onValueChange and updateVersionValue() when editor.children changes.
2. Trigger onSelectionChange and updateVersionSelection() when editor.selection changes.

Fixes #2700
/claim #2700

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[changeset-bot]

🦋 Changeset detected

Latest commit: 0ad3179

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@platejs/core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR