Repository navigation
Remove implicit output buffering from CliApplication - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ob_start()/ob_get_clean()/ob_end_clean()fromCliApplication::run()CliDispatcher, documentation and example usageRationale
CliApplicationintroduced output buffering on 2026-09-27 to make the existing echo-based dispatcher output available as a return string. That global buffering side effect is undesirable for an embeddable CLI library; output ownership remains with the caller.Compatibility
This intentionally changes
CliApplication::run()fromstringtovoid. Exceptions still propagate unchanged.