mirror of
https://github.com/Foundry376/Mailspring.git
synced 2024-09-21 15:56:10 +08:00
1e8fd46342
Summary:
This diff contains a few major changes:
1. Scribe is no longer used for the text editor. It's just a plain contenteditable region. The toolbar items (bold, italic, underline) still work. Scribe was causing React inconcistency issues in the following scenario:
- View thread with draft, edit draft
- Move to another thread
- Move back to thread with draft
- Move to another thread. Notice that one or more messages from thread with draft are still there.
There may be a way to fix this, but I tried for hours and there are Github Issues open on it's repository asking for React compatibility, so it may be fixed soon. For now contenteditable is working great.
2. Action.saveDraft() is no longer debounced in the DraftStore. Instead, firing that action causes the save to happen immediately, and the DraftStoreProxy has a new "DraftChangeSet" class which is responsbile for batching saves as the user interacts with the ComposerView. There are a couple big wins here:
- In the future, we may want to be able to call Action.saveDraft() in other situations and it should behave like a normal action. We may also want to expose the DraftStoreProxy as an easy way of backing interactive draft UI.
- Previously, when you added a contact to To/CC/BCC, this happened:
<input> -> Action.saveDraft -> (delay!!) -> Database -> DraftStore -> DraftStoreProxy -> View Updates
Increasing the delay to something reasonable like 200msec meant there was 200msec of lag before you saw the new view state.
To fix this, I created a new class called DraftChangeSet which is responsible for accumulating changes as they're made and firing Action.saveDraft. "Adding" a change to the change set also causes the Draft provided by the DraftStoreProxy to change immediately (the changes are a temporary layer on top of the database object). This means no delay while changes are being applied. There's a better explanation in the source!
This diff includes a few minor fixes as well:
1. Draft.state is gone—use Message.object = draft instead
2. String model attributes should never be null
3. Pre-send checks that can cancel draft send
4. Put the entire curl history and task queue into feedback reports
5. Cache localIds for extra speed
6. Move us up to latest React
Test Plan: No new tests - once we lock down this new design I'll write tests for the DraftChangeSet
Reviewers: evan
Reviewed By: evan
Differential Revision: https://review.inboxapp.com/D1125
59 lines
2 KiB
Markdown
59 lines
2 KiB
Markdown
## Configuration API
|
|
|
|
### Reading Config Settings
|
|
|
|
If you are writing a package that you want to make configurable, you'll need to
|
|
read config settings via the `atom.config` global. You can read the current
|
|
value of a namespaced config key with `atom.config.get`:
|
|
|
|
```coffeescript
|
|
# read a value with `config.get`
|
|
@showInvisibles() if atom.config.get "editor.showInvisibles"
|
|
```
|
|
|
|
Or you can subscribe via `atom.config.observe` to track changes from any view
|
|
object.
|
|
|
|
```coffeescript
|
|
{View} = require 'space-pen'
|
|
|
|
class MyView extends View
|
|
attached: ->
|
|
@fontSizeObserveSubscription =
|
|
atom.config.observe 'editor.fontSize', (newValue, {previous}) =>
|
|
@adjustFontSize()
|
|
|
|
detached: ->
|
|
@fontSizeObserveSubscription.dispose()
|
|
```
|
|
|
|
The `atom.config.observe` method will call the given callback immediately with
|
|
the current value for the specified key path, and it will also call it in the
|
|
future whenever the value of that key path changes. If you only want to invoke
|
|
the callback when the next time the value changes, use `atom.config.onDidChange`
|
|
instead.
|
|
|
|
Subscription methods return *disposable* subscription objects. Note in the
|
|
example above how we save the subscription to the `@fontSizeObserveSubscription`
|
|
instance variable and dispose of it when the view is detached. To group multiple
|
|
subscriptions together, you can add them all to a
|
|
[`CompositeDisposable`][composite-disposable] that you dispose when the view is
|
|
detached.
|
|
|
|
### Writing Config Settings
|
|
|
|
The `atom.config` database is populated on startup from `~/.atom/config.cson`,
|
|
but you can programmatically write to it with `atom.config.set`:
|
|
|
|
```coffeescript
|
|
# basic key update
|
|
atom.config.set("core.showInvisibles", true)
|
|
```
|
|
|
|
If you're exposing package configuration via specific key paths, you'll want to
|
|
associate them with a schema in your package's main module. Read more about
|
|
schemas in the [config API docs][config-api].
|
|
|
|
[composite-disposable]: https://atom.io/docs/api/latest/CompositeDisposable
|
|
[config-api]: https://atom.io/docs/api/latest/Config
|