You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the work to upgrade sake an API has been created that provides a clear way to format output for HTTP vs for CLI.
That upgrade didn't apply it everywhere that currently outputs to the two places. We should update as much code as we can that outputs to both places so that we're doing things consistently.
In order to achieve this, we may need a PolyOutput as a singleton, which is set to ANSI output for CLI interaction (sake and when phpunit is bootstrapped), and HTML output for all other scenarios.
Acceptance criteria
All code in supported modules that outputs differently based on whether the context is HTTP or CLI uses the new PolyOutput
The text was updated successfully, but these errors were encountered:
GuySartorelli
changed the title
Update various methods which output to both CLI and HTTP responses
(CMS6) Update various methods which output to both CLI and HTTP responses
Oct 10, 2024
GuySartorelli
changed the title
(CMS6) Update various methods which output to both CLI and HTTP responses
(CMS6) Update methods which output to both CLI and HTTP responses
Oct 10, 2024
As part of the work to upgrade sake an API has been created that provides a clear way to format output for HTTP vs for CLI.
That upgrade didn't apply it everywhere that currently outputs to the two places. We should update as much code as we can that outputs to both places so that we're doing things consistently.
The places I'm aware of are:
In order to achieve this, we may need a
PolyOutput
as a singleton, which is set to ANSI output for CLI interaction (sake and when phpunit is bootstrapped), and HTML output for all other scenarios.Acceptance criteria
PolyOutput
The text was updated successfully, but these errors were encountered: