We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently sqlness outputs everything with println!. This is hard to maintain.
println!
Consider a structured way to organize our outputs. Either using existing util like TestReporter from nextest or wrap our own.
TestReporter
No response
The text was updated successfully, but these errors were encountered:
Any user case to collect stdout output?
Sorry, something went wrong.
No for now, just for refactoring
Then I suggest we could define a trait to collect those info
trait Collector { fn append(&self, &str) -> Result<()> fn flush(&self) -> Result<()> }
Not sure if these are enough. This collector may also be exposed to users to replace their println in their sqlness runner
println
No branches or pull requests
Describe This Problem
Currently sqlness outputs everything with
println!
. This is hard to maintain.Proposal
Consider a structured way to organize our outputs. Either using existing util like
TestReporter
from nextest or wrap our own.Additional Context
No response
The text was updated successfully, but these errors were encountered: