Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A way to capture Blueprint errors and output messages #40

Open
adamziel opened this issue Nov 18, 2023 · 3 comments
Open

A way to capture Blueprint errors and output messages #40

adamziel opened this issue Nov 18, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@adamziel
Copy link
Collaborator

adamziel commented Nov 18, 2023

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.

@adamziel adamziel added the enhancement New feature or request label Nov 18, 2023
@seanmorris
Copy link

Rather than passing in a callback, would it be appropriate to expose the information via addEventHandler? then we're not locked into directing the information to a single place.

@dmsnell
Copy link
Member

dmsnell commented Nov 19, 2023

See WordPress/wordpress-playground#605

That PR creates a hook mechanism that could be used to report failures and errors.

@adamziel adamziel mentioned this issue Feb 29, 2024
20 tasks
@adamziel adamziel transferred this issue from WordPress/wordpress-playground Feb 29, 2024
@flexseth
Copy link

flexseth commented Apr 3, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: No status
Development

No branches or pull requests

4 participants