Wp-calypso: Reader Reduxification!

Created on 26 Jan 2017  路  3Comments  路  Source: Automattic/wp-calypso

The time has come for the Reader team to get rid of Flux once and for all.

I thought it might be helpful to create a master issue keeping track of all the major components that need reduxification:

  1. [x] PostStore:
  2. [x] Teams:
  3. [x] Streams:
  4. [x] Subscriptions/Follows:
  5. [x] LikesStore:
  6. [x] Email Subscriptions: https://github.com/Automattic/wp-calypso/pull/12703
  7. [x] Lists:

    • [x] review remaining usage of readerListsStore.get in reader/sidebar and switch to Redux

    • [x] delete codez 馃帀

  8. [x] SiteBlocks:
  9. [x] ReaderSidebar batchfetching:

    • [x] delete all the codez 馃帀

  10. [x] SiteStore:

    • [x] connect components. redux plumbing already in place

  11. [x] TagsStore

    • [x] actions

    • [x] middleware for current following

    • [x] middleware for new follows

    • [x] middleware for unfollowing

    • [x] api validation and potential transformation (fromApi)

    • [x] reducer

    • [x] hook up to ui

    • [x] delete old flux code

Reader [Type] Janitorial

Most helpful comment

It appears that there is code in lib/reader-lists (lists.js and subscriptions.js) that is largely migrated to redux, with just a single usage in the reader sidebar component. I've added a checkbox above to review remaining usage in sidebar prior to removal.

All 3 comments

It appears that there is code in lib/reader-lists (lists.js and subscriptions.js) that is largely migrated to redux, with just a single usage in the reader sidebar component. I've added a checkbox above to review remaining usage in sidebar prior to removal.

DONE! 馃帀

dancing goat

Was this page helpful?
0 / 5 - 0 ratings