Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-12 04:25:31 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/spec-nylas/stores/namespace-store-spec.coffee

33 lines
1.1 KiB
CoffeeScript
Raw Normal View History

fix(mailto): Handle mailto on application launch, populate NamespaceStore synchronously Summary: atom-window `sendMessage` was not the same as `browserWindow.webContents.send`. WTF. Save current namespace to config.cson so that it is never null when window opens Don't re-create thread view on namespace change unless the namespace has changed Tests for NamespaceStore state Push worker immediately in workerForNamcespace to avoid creating two connections per namespace Allow \n to be put into sreaming buffer, but only one Clear streaming buffer when we're reconnecting to avoid processing same deltas twice (because of 400msec throttle) Make `onProcessBuffer` more elegant—No functional changes Test Plan: Run tests! Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1551
2015-05-22 09:08:29 +08:00
_ = require 'underscore'
NamespaceStore = require '../../src/flux/stores/namespace-store'
describe "NamespaceStore", ->
beforeEach ->
fix(spec): Fix memory leak in NamespaceStoreSpec
2015-08-06 00:44:34 +08:00
@instance = null
fix(mailto): Handle mailto on application launch, populate NamespaceStore synchronously Summary: atom-window `sendMessage` was not the same as `browserWindow.webContents.send`. WTF. Save current namespace to config.cson so that it is never null when window opens Don't re-create thread view on namespace change unless the namespace has changed Tests for NamespaceStore state Push worker immediately in workerForNamcespace to avoid creating two connections per namespace Allow \n to be put into sreaming buffer, but only one Clear streaming buffer when we're reconnecting to avoid processing same deltas twice (because of 400msec throttle) Make `onProcessBuffer` more elegant—No functional changes Test Plan: Run tests! Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1551
2015-05-22 09:08:29 +08:00
@constructor = NamespaceStore.constructor
fix(spec): Fix memory leak in NamespaceStoreSpec
2015-08-06 00:44:34 +08:00
afterEach ->
@instance.stopListeningToAll()
fix(mailto): Handle mailto on application launch, populate NamespaceStore synchronously Summary: atom-window `sendMessage` was not the same as `browserWindow.webContents.send`. WTF. Save current namespace to config.cson so that it is never null when window opens Don't re-create thread view on namespace change unless the namespace has changed Tests for NamespaceStore state Push worker immediately in workerForNamcespace to avoid creating two connections per namespace Allow \n to be put into sreaming buffer, but only one Clear streaming buffer when we're reconnecting to avoid processing same deltas twice (because of 400msec throttle) Make `onProcessBuffer` more elegant—No functional changes Test Plan: Run tests! Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1551
2015-05-22 09:08:29 +08:00
it "should initialize current() using data saved in config", ->
state =
"id": "123",
"email_address":"bengotow@gmail.com",
"object":"namespace"
WIP: This is the initial diff for new folders & labels. Summary: There are now two objects, Folders & Labels. These inherit from `Category` (that's what Eben said they were using on the backend). There are two separate tasks. 1. MoveToFolderTask 2. ApplyLabelsTask It turns out that the semantics between the two are quite different. The reverse operation for moving to a folder is a bit tricky. As of 7-8-15, the Tasks are pretty much complete. I need to write tests for them still and do some manual testing in the client. Test Plan: Writing specs Reviewers: bengotow Reviewed By: bengotow Differential Revision: https://phab.nylas.com/D1724
2015-07-16 23:54:20 +08:00
"organization_unit": "label"
fix(mailto): Handle mailto on application launch, populate NamespaceStore synchronously Summary: atom-window `sendMessage` was not the same as `browserWindow.webContents.send`. WTF. Save current namespace to config.cson so that it is never null when window opens Don't re-create thread view on namespace change unless the namespace has changed Tests for NamespaceStore state Push worker immediately in workerForNamcespace to avoid creating two connections per namespace Allow \n to be put into sreaming buffer, but only one Clear streaming buffer when we're reconnecting to avoid processing same deltas twice (because of 400msec throttle) Make `onProcessBuffer` more elegant—No functional changes Test Plan: Run tests! Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1551
2015-05-22 09:08:29 +08:00
spyOn(atom.config, 'get').andCallFake -> state
fix(spec): Fix memory leak in NamespaceStoreSpec
2015-08-06 00:44:34 +08:00
@instance = new @constructor
expect(@instance.current().id).toEqual(state['id'])
expect(@instance.current().emailAddress).toEqual(state['email_address'])
fix(mailto): Handle mailto on application launch, populate NamespaceStore synchronously Summary: atom-window `sendMessage` was not the same as `browserWindow.webContents.send`. WTF. Save current namespace to config.cson so that it is never null when window opens Don't re-create thread view on namespace change unless the namespace has changed Tests for NamespaceStore state Push worker immediately in workerForNamcespace to avoid creating two connections per namespace Allow \n to be put into sreaming buffer, but only one Clear streaming buffer when we're reconnecting to avoid processing same deltas twice (because of 400msec throttle) Make `onProcessBuffer` more elegant—No functional changes Test Plan: Run tests! Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1551
2015-05-22 09:08:29 +08:00
it "should initialize current() to null if data is not present", ->
spyOn(atom.config, 'get').andCallFake -> null
fix(spec): Fix memory leak in NamespaceStoreSpec
2015-08-06 00:44:34 +08:00
@instance = new @constructor
expect(@instance.current()).toEqual(null)
fix(mailto): Handle mailto on application launch, populate NamespaceStore synchronously Summary: atom-window `sendMessage` was not the same as `browserWindow.webContents.send`. WTF. Save current namespace to config.cson so that it is never null when window opens Don't re-create thread view on namespace change unless the namespace has changed Tests for NamespaceStore state Push worker immediately in workerForNamcespace to avoid creating two connections per namespace Allow \n to be put into sreaming buffer, but only one Clear streaming buffer when we're reconnecting to avoid processing same deltas twice (because of 400msec throttle) Make `onProcessBuffer` more elegant—No functional changes Test Plan: Run tests! Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1551
2015-05-22 09:08:29 +08:00
it "should initialize current() to null if data is invalid", ->
spyOn(atom.config, 'get').andCallFake -> "this isn't an object"
fix(spec): Fix memory leak in NamespaceStoreSpec
2015-08-06 00:44:34 +08:00
@instance = new @constructor
expect(@instance.current()).toEqual(null)
Reference in a new issue Copy permalink