Move hasRange to core

[juliankrispel]

Description
Moves hasRange to core Editor, as described in #4160 (comment)

Issue
Fixes #4160

Example
n/a

Context
Moves hasRange from ReactEditor to Editor.
Non-breaking since ReactEditor inherits from Editor,

Checks

• The new code matches the existing patterns and styles.
• The tests pass with yarn test.
• The linter passes with yarn lint. (Fix errors with yarn fix.)
• The relevant examples still work. (Run examples with yarn start.)
• You've added a changeset if changing functionality. (Add one with yarn changeset add.)

[changeset-bot]

🦋 Changeset detected

Latest commit: 882fd5e

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

This PR includes changesets to release 4 packages

Name	Type
slate	Minor
slate-react	Minor

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

[ianstormtaylor]

Thanks for this @juliankrispel! I think this is actually breaking unfortunately because the ReactEditor namespace doesn't inherit all of the helper utilities from the Editor namespace.

I've got a related fix in #4177 that re-implements hasRange as Range.exists since I realized while moving it that there's nothing editor-specific about how it was written. I'm going to close in favor of that one, hope that makes sense. (Sorry for not properly linking that issue to give you a heads up that it would be solved!)

[juliankrispel]

Thanks for this @juliankrispel! I think this is actually breaking unfortunately because the ReactEditor namespace doesn't inherit all of the helper utilities from the Editor namespace.

I've got a related fix in #4177 that re-implements hasRange as Range.exists since I realized while moving it that there's nothing editor-specific about how it was written. I'm going to close in favor of that one, hope that makes sense. (Sorry for not properly linking that issue to give you a heads up that it would be solved!)

no worries thanks for clearing that up