WordPress / WordPress/wp-consent-level-api
Interface stability
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 92
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 7
Description
In the medium term, we need to think about API stability and migration paths and deprecating functions/parameters.
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
The issue does not name files, tests, or an entry point. First define the API stability risks, migration paths, and functions or parameters requiring deprecation; done would be an agreed, actionable plan for handling those changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100