* Experimental release to see if CustomTypes holds up through a publish
* Add experimental release script
* Fix lint
* v0.60.5-alpha.0
* Allow null properties in setNodes
* v0.60.6-alpha.0
* Revert null properties on Transforms.setNodes
* v0.60.7-alpha.0
* Update examples to use custom Element and Text with discriminated unions
* Add documentation for using TypeScript improvements
* Be explicit about typescript version in package.json
* Force lerna bootstrap to fix build issues on CI and fix a few type examples
* Add slate devDependencies with * back
* v0.60.7
* Switch to a non prerelease version to fix lerna not linking in root
* Add documentation for not using prerelease versions and on how to create experimental releases
* Try removing lerna bootstrap and see if it works
* mvp implementation for working with non-global window instances
* remove unused element renderer
* fix typo in comment
* fix wrong example reference
* Add @babel/helper-call-delegate to fix build error
Co-authored-by: Lukas Buenger <lukasbuenger@gmail.com>
This PR adds better TypeScript types into Slate and is based on the proposal here: https://github.com/ianstormtaylor/slate/issues/3725
* Extend Slate's types like Element and Text
* Supports type discrimination (ie. if an element has type === "table" then we get a reduced set of properties)
* added custom types
* files
* more extensions
* files
* changed fixtures
* changes eslint file
* changed element.children to descendant
* updated types
* more type changes
* changed a lot of typing, still getting building errors
* extended text type in slate-react
* removed type assertions
* Clean up of custom types and a couple uneeded comments.
* Rename headingElement-true.tsx.tsx to headingElement-true.tsx
* moved basetext and baselement
* Update packages/slate/src/interfaces/text.ts
Co-authored-by: Brent Farese <25846953+BrentFarese@users.noreply.github.com>
* Fix some type issues with core functions.
* Clean up text and element files.
* Convert other types to extended types.
* Change the type of editor.marks to the appropriate type.
* Add version 100.0.0 to package.json
* Revert "Add version 100.0.0 to package.json"
This reverts commit 329e44e43d968700655b1c46f968bfd3147e7339.
* added custom types
* files
* more extensions
* files
* changed fixtures
* changes eslint file
* changed element.children to descendant
* updated types
* more type changes
* changed a lot of typing, still getting building errors
* extended text type in slate-react
* removed type assertions
* Clean up of custom types and a couple uneeded comments.
* Rename headingElement-true.tsx.tsx to headingElement-true.tsx
* moved basetext and baselement
* Update packages/slate/src/interfaces/text.ts
Co-authored-by: Brent Farese <25846953+BrentFarese@users.noreply.github.com>
* Fix some type issues with core functions.
* Clean up text and element files.
* Convert other types to extended types.
* Change the type of editor.marks to the appropriate type.
* Run linter.
* Remove key:string uknown from the base types.
* Clean up types after removing key:string unknown.
* Lint and prettier fixes.
* Implement custom-types
Co-authored-by: mdmjg <mdj308@nyu.edu>
* added custom types to examples
* reset yarn lock
* added ts to fixtures
* examples custom types
* Working fix
* ts-thesunny-try
* Extract interface types.
* Fix minor return type in create-editor.
* Fix the typing issue with Location having compile time CustomTypes
* Extract types for Transforms.
* Update README.
* Fix dependency on slate-history in slate-react
Co-authored-by: mdmjg <mdj308@nyu.edu>
Co-authored-by: Brent Farese <brentfarese@gmail.com>
Co-authored-by: Brent Farese <25846953+BrentFarese@users.noreply.github.com>
Co-authored-by: Tim Buckley <timothypbuckley@gmail.com>
* fix index.js main bundles to be commonjs instead of modules
* Change rm -rf to rimraf to be cross os compatible
* add rimraf as dependency
Co-authored-by: damareyoh <chackerman@wsu.edu>
* fix import extensions of eslint
* revert next.config.cjs
* fix eslint globbing
* add migrating to docs’ sidebar
* fix prettier error on Contributing.md
* put quotes for glob matching for windows user
* remove type: module from package.json
* first stab at removing leaves with tests passing
* fixes
* add iterables to the element interface
* use iterables in more places
* update examples to use iterables
* update naming
* fix tests
* convert more key-based logic to paths
* add range support to iterables
* refactor many methods to use iterables, deprecate cruft
* clean up existing iterables
* more cleanup
* more cleaning
* fix word count example
* work
* split decoration and annotations
* update examples for `renderNode` useage
* deprecate old DOM-based helpers, update examples
* make formats first class, refactor leaf rendering
* fix examples, fix isAtomic checking
* deprecate leaf model
* convert Text and Leaf to functional components
* fix lint and tests
* Allow the dev server to work for non localhost host
* Refactored set-selection-from-dom into utils as prep for Android support
* Show debug onInput at start if triggered
* Added and refactored to use set-text-from-dom-node with improved set selection after input
* Remove unnecessary console.log in set-text-from-dom-node
* Fixes to pass linter
* Adds basic composition to Android API27 including fixing one bug where compositionStart does not fire
* Fix some of the enter handling in API 27 and 28
* Add fixes for API 25
* Add debug for slate:update instead of separate render and updateSelection
* Add API 26 fix for ignoring all but Enter in onKeyDown
* Fix enter on Android 26 and 27
* Revert onSelect bug. Editor API 26 and 27 stable-ish
* Fix enter at beginning and end of word in API 26 and 27
* Fix enter handling at end of line API 26 and 27
* Fix reversion of enter bug when not at end of line
* Rename enter to linefeed which is more accurate
* Fix backspace on Android 27 and 28
* Fix enter at end of line then backspace then enter bug in API 26 and 27
* Refactor to simplify reading code
* Refactor to use executor and fix the suggestion problem
* Fix multi point edit in API 27/28
* Update Android documentation on enter handling
* Fix enter in API 26/27 and document 4 different enter cases
* Refactor partial into SlateSnapshot
* Complete SlateSnapshot refactor
* Remove unnecessary plugin comments
* Add smoke tests
* Rename smoke tests to composition in exmaples
* Fix API28 split join and insertion
* Fix space then backspace in middle of word bug in API 28
* Add text for middle word space and backspace bug
* Add note that the space backspace bug does not exist on API 27
* Fix 'It me. No.' bug in API 26/27
* Fix comments
* Update comments to fit Slate style guide
* Move a debug statement
* Fix zero-width selection placement bug.
* Fix 'it is' then enter in middle of 'it' bug
* Partial fix of enter, backspace, enter in word
* Add and fix comments. Fix selection in zero-width for API26-27
* Fix linting
* Fix documentation
* Remove snapback from packages
* Remove snapback from yarn.lock
* Rename SlateSnapshot to DomSnapshot
* Remove guard on DomSnapshot apply method
* Remove debug plugin from plugins/dom
* Remove unnecessary comment in content.js componentDidUpdate
* Remove closest and add function into dom-snapshot directly
* Remove unused DebugPlugin
* Move Android detection related code into slate-dev-environment
* Capitalize to Number in JSDoc
* Add API version and Input Events Level 2 for Android
* Add input events level 2 for android without matching api version
* Fix line failures
* Allow the dev server to work for non localhost host
* Refactored set-selection-from-dom into utils as prep for Android support
* Show debug onInput at start if triggered
* Added and refactored to use set-text-from-dom-node with improved set selection after input
* Remove unnecessary console.log in set-text-from-dom-node
* Fixes to pass linter
* Adds basic composition to Android API27 including fixing one bug where compositionStart does not fire
* Fix some of the enter handling in API 27 and 28
* Add fixes for API 25
* Add debug for slate:update instead of separate render and updateSelection
* Add API 26 fix for ignoring all but Enter in onKeyDown
* Fix enter on Android 26 and 27
* Revert onSelect bug. Editor API 26 and 27 stable-ish
* Fix enter at beginning and end of word in API 26 and 27
* Fix enter handling at end of line API 26 and 27
* Fix reversion of enter bug when not at end of line
* Rename enter to linefeed which is more accurate
* Fix backspace on Android 27 and 28
* Fix enter at end of line then backspace then enter bug in API 26 and 27
* Refactor to simplify reading code
* Refactor to use executor and fix the suggestion problem
* Fix multi point edit in API 27/28
* Update Android documentation on enter handling
* Fix enter in API 26/27 and document 4 different enter cases
* Refactor partial into SlateSnapshot
* Complete SlateSnapshot refactor
* Remove unnecessary plugin comments
* Add smoke tests
* Rename smoke tests to composition in exmaples
* Fix API28 split join and insertion
* Fix space then backspace in middle of word bug in API 28
* Add text for middle word space and backspace bug
* Add note that the space backspace bug does not exist on API 27
* Fix 'It me. No.' bug in API 26/27
* Fix comments
* Update comments to fit Slate style guide
* Move a debug statement
* Fix zero-width selection placement bug.
* Fix 'it is' then enter in middle of 'it' bug
* Partial fix of enter, backspace, enter in word
* Add and fix comments. Fix selection in zero-width for API26-27
* Fix linting
* Fix documentation
* Remove snapback from packages
* Remove snapback from yarn.lock
#### Is this adding or improving a _feature_ or fixing a _bug_?
_bug_
#### What's the new behavior?
Fix behavior for <kbd>shift + left</kbd> and <kbd>shift + right</kbd>. Now they will correctly move forward / backward.
#### How does this change work?
turns out that the hotkey `'left'` would also pick up with a modifier key `'shift+left'` so checking for `Hotkeys.isExtendForward()` needs to come before `Hotkeys.isMoveForward()` and it needs to short circuit with `return true`. Likewise for backward.
#### Have you checked that...?
<!--
Please run through this checklist for your pull request:
-->
* [x] The new code matches the existing patterns and styles.
* [x] The tests pass with `yarn test`.
* [x] The linter passes with `yarn lint`. (Fix errors with `yarn prettier`.)
* [x] The relevant examples still work. (Run examples with `yarn watch`.)
#### Does this fix any issues or need any specific reviewers?
Fixes: #2307
Reviewers: @ianstormtaylor
#### Is this adding or improving a _feature_ or fixing a _bug_?
Debt.
#### What's the new behavior?
This removes almost all existing deprecations from previous API changes, to save on filesize and reduce complexity in the codebase going forward.
It also changes from using the `slate-dev-logger` to using the Facebook-inspired `slate-dev-warning` which can be compiled out of production builds with [`babel-plugin-dev-expression`](https://github.com/4Catalyzer/babel-plugin-dev-expression) to save even further on file size.
The only deprecations it keeps are in the `fromJSON` methods for data model changes like `.kind` and `.leaves` which may still may not have been migrated in databases, since this is a bigger pain point.
#### Have you checked that...?
* [x] The new code matches the existing patterns and styles.
* [x] The tests pass with `yarn test`.
* [x] The linter passes with `yarn lint`. (Fix errors with `yarn prettier`.)
* [x] The relevant examples still work. (Run examples with `yarn watch`.)
#### Does this fix any issues or need any specific reviewers?
Fixes: #1922Fixes: #2105Fixes: #646Fixes: #2109Fixes: #2107Fixes: #2018
#### Is this adding or improving a _feature_ or fixing a _bug_?
Improvement.
#### What's the new behavior?
This deprecates the `node.isVoid` property in favor of using `schema.isVoid(node)`, which will allow us to remove the hardcoded "void" concept from the data model, and have it depend on the schema instead.
This allows you to build different kinds of editors, with different void semantics, depending on your use case, without having this information hardcoded in the data itself. Even switching the `isVoid` semantics on the fly based on a user toggling a setting for example.
#### How does this change work?
This is the first step, which just deprecates `node.isVoid`, and provides the new alternative of `schema.isVoid(node)`, while still using the `isVoid` value of nodes under the covers.
The next step is to change the logic to search the schema for real, and completely remove the `isVoid` value from nodes.
#### Have you checked that...?
<!--
Please run through this checklist for your pull request:
-->
* [x] The new code matches the existing patterns and styles.
* [x] The tests pass with `yarn test`.
* [x] The linter passes with `yarn lint`. (Fix errors with `yarn prettier`.)
* [x] The relevant examples still work. (Run examples with `yarn watch`.)
* Trying to use memoization and upgrade to react v16
* Fix error
* Fix error
* Fix handlers error
* Add annotation
* Remove EventHandlers
* No state
* Remove un-necessary polyfill
* Remove un-necessary polyfill
* Remove un-necessary handlers settings
* Early Return
* Fix Early Return
* Fix onChange
* Do not run onChange stack twice on same change
* Update annotation
* Better sense of resolve++
* Cache value in onChange and didMount
* Remove un-necessary rechack
* Renaming
* Remove change in leaf.js
* Handlers as this.handlers
* do not re-initialize change in onChange
* Re-run onChange stack only when change happens
* Update value when stack changes
* Rename to memoize-one
* queue changes
* Unify interface
* Fix bug
* Add document
* Remove id
* Do not use map
* Fix bug
* Fix eslint
* Fix update when props.value changes
* Add annotation
* Fix stack
* Inline queueChange
* Restore onChange
* restore onChange
* Refactor change and onChange
* Use onChange as the single interface for update
* Do not flushChange if inside event
* Give a warning about synchronous editor.change call
* Change isInChange in editor.change
* refactor resolution and tmp logic, cleanup code
#### Is this adding or improving a _feature_ or fixing a _bug_?
Example.
#### What's the new behavior?
Adds a new example that is an input event logger, for more easily seeing which input/keyboard/selection events are firing when editing in a Slate editor.
#### Have you checked that...?
* [x] The new code matches the existing patterns and styles.
* [x] The tests pass with `yarn test`.
* [x] The linter passes with `yarn lint`. (Fix errors with `yarn prettier`.)
* [x] The relevant examples still work. (Run examples with `yarn watch`.)
* Run mocha test with module alias
* Running test with babel module alias
* Fix model alias
* Fix model alias
* Resolve module alias
* Running test with babel module alias
* Connect to codecov
* add codecov to travis
* stop if yarn test has errors
* Still cannot collect data from slate modules
* Try to check whether it works with codecov
* Move config to nycrc
* Remove nyc require
* Update nyc to use src
* better before_script
#### Is this adding or improving a _feature_ or fixing a _bug_?
Feature.
#### What's the new behavior?
This pull request adds paths to `Range` objects, including the selection. The paths and keys are kept in sync automatically, so that you can use whichever is ideal for your use case.
This should allow us to use paths for lots of the internal logic, which are much quicker to work with than keys since they avoid having to lookup the key in the document and can just traverse right to the node in question.
#### How does this change work?
`Range` objects have two new properties:
```js
range.anchorPath
range.focusPath
```
(Eventually these will be `range.anchor.path` and `range.focus.path` when points are introduced.)
When operations occur and whenever ranges are created/normalized, the paths are updated and kept in sync with the keys.
#### Have you checked that...?
<!--
Please run through this checklist for your pull request:
-->
* [x] The new code matches the existing patterns and styles.
* [x] The tests pass with `yarn test`.
* [x] The linter passes with `yarn lint`. (Fix errors with `yarn prettier`.)
* [x] The relevant examples still work. (Run examples with `yarn watch`.)
#### Does this fix any issues or need any specific reviewers?
Fixes: https://github.com/ianstormtaylor/slate/issues/1408
Fixes: https://github.com/ianstormtaylor/slate/issues/1567
