WordPress / WordPress/php-toolkit
A way to capture Blueprint errors and output messages
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 61
- Forks
- 21
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 7
Description
Currently there's no easy way to capture output messages and warnings/error messages coming from Blueprints. Let's add one. That could be as simple as accepting an onError(step: Step, message: string, isFatal: boolean); callback and onOutput(step: Step, message: string); callback. Nuance: Errors may also come from Resources and other non-step sources.
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 the Blueprint execution and message-handling entry points, then trace how Resources and other non-step sources report errors. Done means defining and documenting a consistent way to capture output, warnings, and fatal errors from all relevant sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100