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
Facelift for Queries Generator error logging (#866) #874
base: master
Are you sure you want to change the base?
Facelift for Queries Generator error logging (#866) #874
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for jumping in here! Most of my feedback is just formatting and idiom/style things, I like the general shape.
Do you mind also including a screenshot for some review and feedback?
Co-authored-by: Scott Trinh <scottyparade@gmail.com>
Co-authored-by: Scott Trinh <scottyparade@gmail.com>
Co-authored-by: Scott Trinh <scottyparade@gmail.com>
My latest experience with this change, is that now it feels kind of redundant to print error messages twice: "inline" and aggregated at the bottom. Maybe it's enough to indicate "inline" errors simply with red color (and giving the detailed error in summary)? And one more thing: to reduce messiness, put a separator in between error messages? |
Yeah, that looks great! |
Yeah, either a separator or just a new line works for me, I trust your judgement here. |
There are still a couple of changes needed to be make in order to make |
Sorry to ask it here, but is there an industry standard way of keeping a link to my forked |
You can use |
Just a little proposal to improve visibility on the outcome of the generator (until a more advanced solution like TAP is implemented)