Mailspring/packages/client-app/spec/tasks/change-starred-task-spec.coffee

Task = require('../../src/flux/tasks/task').default
Thread = require('../../src/flux/models/thread').default
ChangeStarredTask = require('../../src/flux/tasks/change-starred-task').default

describe 'ChangeStarredTask', ->
  describe "description", ->
    it 'should include special cases for changing starred', ->
      threads = [
        new Thread(id:"id-1")
        new Thread(id:"id-2")
        new Thread(id:"id-3")
      ]
      task = new ChangeStarredTask({threads:threads, starred: true})
      expect(task.description()).toEqual("Starred 3 threads")
      task = new ChangeStarredTask({thread: threads[0], starred: true})
      expect(task.description()).toEqual("Starred")
      task = new ChangeStarredTask({threads:threads, starred: false})
      expect(task.description()).toEqual("Unstarred 3 threads")
      task = new ChangeStarredTask({thread: threads[0], starred: false})
      expect(task.description()).toEqual("Unstarred")
feat(babel6): Convert to use new es6 require syntax 2016-05-04 07:42:28 +08:00			`Task = require('../../src/flux/tasks/task').default`
			`Thread = require('../../src/flux/models/thread').default`
			`ChangeStarredTask = require('../../src/flux/tasks/change-starred-task').default`
perf(*): Add indexes, optimize "shouldAcceptModel", optimize Tasks Summary: Consolidate the smarts from ChangeFolderTask into a generic ChangeMailTask ChangeMailTask: - only makes requests for threads / messages that actually changed - handles incrementing / decrementing locks - writes changes to the database in a single pass, and only writes modified models - encapsulates the undo state that was built into ChangeFolderTask This change means that ChangeLabelsTask enjoys the same "smarts" as ChangeFolderTask. Label changes resulting in no-ops do not create web requests, you can undo label changes and they go back to the correct previous state. Replace "UpdateThreadsTask" and "UpdateNylasObjectsTask" with subclasses based on the same code used for folder/labels This means that the naming and parameter sets are consistent for all thread/message changing tasks. It also means that starring/marking as use the same (tested) business logic and starring 999 already-starred threads doesn't create 999 requests. Go away DraftCountStore - nobody wants you in secondary windows Add "Debug query plans" option which prints out the steps the database is taking. Look for "SCAN" to now you're having a bad time. Make "version" field queryable, when we receive deltas/API response, find all versions of existing models in a single query without loading or parsing the objects Contact: Add index for lookup by email Label: add index for lookup by name Message: Add index for message body join table Test Plan: Run tests Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D1840 2015-08-06 06:53:08 +08:00
			`describe 'ChangeStarredTask', ->`
			`describe "description", ->`
			`it 'should include special cases for changing starred', ->`
			`threads = [`
			`new Thread(id:"id-1")`
			`new Thread(id:"id-2")`
			`new Thread(id:"id-3")`
			`]`
			`task = new ChangeStarredTask({threads:threads, starred: true})`
			`expect(task.description()).toEqual("Starred 3 threads")`
			`task = new ChangeStarredTask({thread: threads[0], starred: true})`
			`expect(task.description()).toEqual("Starred")`
			`task = new ChangeStarredTask({threads:threads, starred: false})`
			`expect(task.description()).toEqual("Unstarred 3 threads")`
			`task = new ChangeStarredTask({thread: threads[0], starred: false})`
			`expect(task.description()).toEqual("Unstarred")`