-
-
Notifications
You must be signed in to change notification settings - Fork 7
Add proper issue template for bug reports #99
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
Conversation
Simon-Laux
left a comment
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.
I think the most important are the test cases, it should explain how to get them:
https://deltachat.github.io/message-parser/
Test case should be ideally input, expected output AST and actual output AST.
we could change the demo site, like add a copy button to the field where the AST is displayed. |
Co-authored-by: Simon Laux <Simon-Laux@users.noreply.github.com>
Co-authored-by: Simon Laux <Simon-Laux@users.noreply.github.com>
|
Anyways I'm not really sure that we need an issue template. I'm glad if people report bugs, they might not if we increase the barrier of entry / time cost of filing bugs. |
|
not worth the effort for now, we can consider increasing friction, when we get too many bug reports. |
How do we test it without merging? Also, is it possible to provide a better interface for test cases?