Evan Morikawa 2aae075126 refactor(contenteditable): new ContenteditableExtension API ... Summary: This provides a new API for `ContenteditableExtension`s. Instead of manually manipulating the raw DOM and `Selection` objects, there's a new `Editor` interface that encapsulates it and provides helper methods. You can now do: editor.select(someNode).createLink("foo").collapseToEnd() Now raw methods like `execCommand` ONLY show up in the `Editor` interface as well as most of the raw `Selection` APIs. There are also more integration tests :) Another major goal was cleaning up the contenteditable file itself. To that end: 1. The DOMNormalizer got pulled out into its own extension 1. The TabManager is now its own extension 1. Url wrangling got moved into the FloatingToolbar control 1. There is now the concept of a `ContenteditableService`, which are tightly-couple blocks of code separated out into logical units. These are dependent on the core state, innerState, and props and are not full extensions. 1. `MouseService` now handles all the click event logic 1. `ClipboardService` was modified to the new service architecture Test Plan: script/grunt run-integration-tests Reviewers: drew, juan, bengotow Reviewed By: juan, bengotow Differential Revision: https://phab.nylas.com/D2367		2015-12-21 19:58:01 -08:00
..
client-actions.es6
config-helper.es6
contenteditable-test-harness.es6	refactor(contenteditable): new ContenteditableExtension API	2015-12-21 19:58:01 -08:00
n1-launcher.es6
shared-assertions.es6