Declare missing useSelect dependencies
Open
Nobody has claimed this yet.
Maintenance & Fixes
wp-parsely
- Dominant language
- PHP
- Stars
- 66
- Forks
- 36
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Is your feature request related to a problem?
Currently, not all our useSelect calls contain specific dependency arrays. However, according to this article, we should always declare useSelect dependencies.
Describe the solution you'd like
See the dependencies we should declare in every useSelect call, and update our code where applicable.
Contributor guide
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.
Research direction
Search the repository for every useSelect call and compare each one with the dependency guidance in the linked WordPress article. Declare the applicable dependencies for all calls, then verify that the affected code and existing checks still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, wordpress
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100