Restructure WPR to match BWPU
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- playwright, typescript
- Domain
- build-system, testing-qa
Research direction
Start by inspecting the existing src/ tree, especially the backwpup/common, features, support, and utils folders, and identify the current shared features and support functions. Done means WPR has the same internal structure as backwpup, while common features, support functions, and utilities are placed in the appropriate parent-level folders.
Written by the indexing model from the issue text.
Description
- Currently inside src, we have the BWPU folder ,which has some folders inside it i.e, features, common, steps..etc
- We need to have the same structure for WPR and common functions between WPR and BWPU to be moved to a folder inside the parent folder
Current
src/
├── config/
├── features/
├── support/
│ ├── results/
│ ├── steps/
│ └── ...
├── utils/
├── backwpup/
│ ├── common
│ ├── features
│ ├── support
│ ├── utils
│ └── ...
└── ...
Expected
src/
├── config/
├── features/ ======>for common features i.e install, activate , delete
├── support/ ====> for common support functions
│ ├── results/
│ ├── steps/
│ └── ...
├── utils/
├── backwpup/
│ ├── common
│ ├── features
│ ├── support
│ ├── utils
│ └── ...
├── wp-rocket/
│ ├── common
│ ├── features
│ ├── support
│ ├── utils
│ └── ...
└── ...
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wp-media/wp-rocket-e2e
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
wp-media/wp-rocket-e2e#407 ·
-
Fatal guard e2e plan Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wp-media/wp-rocket-e2e#396 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
wp-media/wp-rocket-e2e#408 · 1 comment ·
-
Flaky test round 3 Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
wp-media/wp-rocket-e2e#406 · 4 comments ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 68/100
wp-media/wp-rocket-e2e#399 · 3 comments ·
All issues in wp-media/wp-rocket-e2e
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·