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
{{ message }}
This repository was archived by the owner on Aug 17, 2025. It is now read-only.
Without using output buffering, the body of the response will be output to the terminal when running the test.
It would be great if the \Phlyty\App::run() method included a parameter to send the response (which defaults to true for backwards compatibility). When this parameter is set to false, the $this->response()->send() line would not be called. This would allow me to run the app without sending the response output by simply calling $this->app->run(false). For bonus points, it would be nice if a) the \Phlyty\App::run() method returned the response object and b) I could pass a more generic version of the request object to the app for functional testing purposes.
The last line of the
\Phlyty\App::run()method sends the response:The resultant output makes it difficult to perform functional testing. Take the following test case as an example:
Without using output buffering, the body of the response will be output to the terminal when running the test.
It would be great if the
\Phlyty\App::run()method included a parameter to send the response (which defaults totruefor backwards compatibility). When this parameter is set tofalse, the$this->response()->send()line would not be called. This would allow me to run the app without sending the response output by simply calling$this->app->run(false). For bonus points, it would be nice if a) the\Phlyty\App::run()method returned the response object and b) I could pass a more generic version of the request object to the app for functional testing purposes.