Automattic / Automattic/woocommerce-services

[Architecture] Spike - Identify work needed for migrating `state`

Open
#1,699 0 comments 0 reactions 0 assignees View on GitHub
[Pri] High [Type] Enhancement woocommerce-services
Dominant language
JavaScript
Stars
112
Forks
35
Avg merge
3d 1h
Merged PRs (30d)
14

Description

In the [PoC branch](https://github.com/Automattic/woocommerce-services/compare/tweak/poc-architecture-meetup-v2) we still have `wp-calypso` as a folder (but not a submodule). It isn't really calypso, just a very small subset of it. Refer to `WooCommerce Services Architecture` p2 for more info.

The goal of this spike is to figure out what needs to be done in order to migrate `state` out of that folder and into the extension root folder. It'll probably require some roundtable discussion.

Contributor guide

Open the contributing guide

Research direction

Open the PoC branch comparison and the “WooCommerce Services Architecture” document, page 2; inspect the wp-calypso folder and its state subset. Identify the work needed to move state into the extension root and use the proposed roundtable discussion to resolve scope. Done means an agreed migration checklist.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
developer-experience
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.