WordPress / WordPress/php-toolkit
Blueprints: Constraints
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
Right now Blueprints only support preferredVersions:
{
"preferredVersions": {
"php": "7.4",
"wp": "5.9"
}
}
It would be lovely to support explicit constraints. For example:
{
"constraints": [
"php < 8.0",
"wp >= 6.2"
]
}
This way:
- Playground could only show the supported PHP and WP versions in the version picker
- Merging multiple Blueprints would result in a runtime that supports all partial Blueprints
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
No files, tests, or entry points are named. Start by locating Blueprint handling and the existing preferredVersions implementation, then determine how explicit PHP and WordPress constraints should be represented, combined, and exposed to version selection; done means the example constraints work and merged Blueprints retain all required constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100