WordPress / WordPress/plugin-check
Communicate runtime check eligibility to users
Open
Nobody has claimed this yet.
[Type] Enhancement
- Dominant language
- PHP
- Stars
- 362
- Forks
- 126
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 22
Description
In order to perform runtime checks, a few conditions must be met:
- Plugin Check must be "initialized early" (using WP-CLI I presume) OR the object-cache drop-in must exist
- AND the plugin under test must be active
This is not communicated at all when running Plugin Check either via WP-CLI or in WordPress admin.
If the plugin is not active, then the runtime checks will simply not be run, without you ever noticing it.
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
Start by tracing how runtime checks are invoked through the WP-CLI and WordPress admin paths. Reproduce the case where the plugin under test is inactive, and check the initialization or object-cache conditions described in the issue. Done means users are told when runtime checks are ineligible or skipped in both interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100