-
Notifications
You must be signed in to change notification settings - Fork 14
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
Enumerate common error/warning messages #312
Labels
Milestone
Comments
vazexqi
pushed a commit
that referenced
this issue
Aug 17, 2011
Currently the comment is truncated to ATTRIBUTE_LENGTH_LIMIT = 10 000 characters. Usually only the first few lines of the comments are sufficient to provide context. This commit belongs to issue #312.
Would you add the query we wrote for listing the error messages of "change method signature" to |
reprogrammer
added a commit
that referenced
this issue
Aug 18, 2011
This commit belongs to issue #312.
vazexqi
pushed a commit
that referenced
this issue
Aug 27, 2011
We need this information to provide more context during the interview process. Some of the selection information cannot be retrieved via replaying via CodingTracker so this is the only way to retrieve it. This commit belongs to issue #312.
reprogrammer
added a commit
that referenced
this issue
Nov 18, 2011
This commit belongs to issue #312.
reprogrammer
added a commit
that referenced
this issue
Nov 19, 2011
This commit belongs to issue #312.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have captured the error/warning messages from refactorings. This allows us to determine what are the common errors/warnings that users encounter and perhaps offer better interfaces for quickly notifying of such errors, preventing such errors, etc. So far, no other work has tried to categorize the common error/warning messages that developers encounter while using tools.
The list of code changes needed to support this analysis will be documented here. The actual results will be written in our wiki page.
The text was updated successfully, but these errors were encountered: