WordPress / WordPress/wp-consent-level-api
Interface consistency
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 92
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 7
Description
We should try to tighten the interface to be more consistent (both internally and with other Core APIs). Potentially, this goal is in conflict with #44.
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.
Research direction
Start by reviewing issue #44 and the repository's existing public API conventions. No files or tests are named, so map the affected interfaces before defining the scope; done requires an agreed consistency plan that resolves the possible conflict with #44.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100