[525304] Fix method call in Diagnostic.INFO case (DotJavaValidator.java) #6
Conversation
This file contains 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
|
You are right. Could you please raise a Bugzilla for this, and reference it in the commit. This is how contributions will get 'traced' to releases. |
|
Thank you for the info, I wasn't sure if its too minor to write a bug report. I tried just now and got an internal server error on bugs.eclipse.org, I will retry later. |
- Changed the method in DotJavaValidator.checkValidAttributeValue:119 Diagnostic.INFO case to match in issue severity (acceptInfo instead of acceptError) Signed-off-by: Zoey Gerrit Prigge <zoey.prigge@uni-duesseldorf.de> Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=525304
prggz
force-pushed
the
NONE_Typo_error_validation_attributes
branch
from
a3da36d
to
25bd522
Compare
prggz
changed the title
|
@nyssen I have updated the bug reference now. |
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.
I noticed this working on the recordLabelValidation. I think this is a simple typo. Would be great if you could have a look. Thanks!