Mailspring/internal_packages/account-sidebar/lib/account-sidebar-sections.coffee

{Actions, SyncbackCategoryTask, DestroyCategoryTask} = require 'nylas-exports'

class AccountSidebarSection

  constructor: ({@label, @iconName, @items} = {}) ->


class CategorySidebarSection extends AccountSidebarSection

  constructor: ({@label, @iconName, @account, @items} = {}) ->

  onCreateItem: (displayName) =>
    return unless @account
    CategoryClass = @account.categoryClass()
    category = new CategoryClass
      displayName: displayName
      accountId: @account.id
    Actions.queueTask(new SyncbackCategoryTask({category}))

module.exports = {
  AccountSidebarSection
  CategorySidebarSection
}
AccountSidebar package refactor: - Creates OutlineView generic component and uses that instead of custom code - Refactors AccountSidebarStore: - Split the generation of the state tree into smaller functions - Adds different types of account sidebar items and sections, which contain logic and props necessary to be rendered as OutlineViewItems, and removes that logic from the store - Removes WorkspaceStore.SidebarItem and removes the ability to register new sidebar items. If people want to add something to the sidebar they can just register a Component via the component registry and use the OutlineView component - Removes the DraftListSidebarItem, which was basically duplicated code for an item but with a different data source. This is now handled generically by the account sidebar by rendering OutlineViewItems with different props and handlers - Clean ups here and there: - TODO - Add AccountSwitcher - Revisit calculation and generation of the state tree. Should the parent store contain and update the entire state all the time. Should separate items inside the tree have their own data sources? - This would avoid having the AccountSidebarStore listen to a bunch of different other stores, and the specific logic wold be contained inside each item type. 2016-01-16 08:27:57 +08:00			`{Actions, SyncbackCategoryTask, DestroyCategoryTask} = require 'nylas-exports'`

			`class AccountSidebarSection`

			`constructor: ({@label, @iconName, @items} = {}) ->`


			`class CategorySidebarSection extends AccountSidebarSection`

			`constructor: ({@label, @iconName, @account, @items} = {}) ->`

Minor fixes and style updates 2016-01-19 03:39:53 +08:00			`onCreateItem: (displayName) =>`
AccountSidebar package refactor: - Creates OutlineView generic component and uses that instead of custom code - Refactors AccountSidebarStore: - Split the generation of the state tree into smaller functions - Adds different types of account sidebar items and sections, which contain logic and props necessary to be rendered as OutlineViewItems, and removes that logic from the store - Removes WorkspaceStore.SidebarItem and removes the ability to register new sidebar items. If people want to add something to the sidebar they can just register a Component via the component registry and use the OutlineView component - Removes the DraftListSidebarItem, which was basically duplicated code for an item but with a different data source. This is now handled generically by the account sidebar by rendering OutlineViewItems with different props and handlers - Clean ups here and there: - TODO - Add AccountSwitcher - Revisit calculation and generation of the state tree. Should the parent store contain and update the entire state all the time. Should separate items inside the tree have their own data sources? - This would avoid having the AccountSidebarStore listen to a bunch of different other stores, and the specific logic wold be contained inside each item type. 2016-01-16 08:27:57 +08:00			`return unless @account`
			`CategoryClass = @account.categoryClass()`
			`category = new CategoryClass`
			`displayName: displayName`
			`accountId: @account.id`
			`Actions.queueTask(new SyncbackCategoryTask({category}))`

			`module.exports = {`
			`AccountSidebarSection`
			`CategorySidebarSection`
			`}`