-
Notifications
You must be signed in to change notification settings - Fork 26
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
Review LSP4Jakarta diagnostic code and resolve remaining issues with matching qualified class names. #879
Comments
I have started reviewing the LSP4Jakarta diagnostic collectors. Will document additional discoveries here. |
Should also delete the unused non-qualified class names from |
Analysis of |
This method should only use the qualified names to determine if a class is a wrapper. |
All tasks have been completed on this epic. |
While reviewing #860 I noticed additional issues in the way that the LSP4Jakarta diagnostic collectors are matching qualified names. Specifically
BeanValidationDiagnosticsCollector
is checking if a type name ends with the simple name of several classes (constants defined inBeanValidationConstants
).For instance this code
type.getCanonicalText().endsWith(BIG_DECIMAL)
was likely intended to only matchjava.math.BigDecimal
but will match aBigDecimal
in any Java package (e.g.com.example.BigDecimal
). There may yet still be other instances of qualified names that are not processed correctly. We should thoroughly review the code to ensure that we fully address these issues once and for all.Code review check list for each of the diagnostic collectors within
io.openliberty.tools.intellij.lsp4jakarta.lsp4ij
:ManagedBeanConstants
DependencyInjectionConstants
ServletConstants
java.lang
package. Should remove unused unqualified names fromWebSocketConstants
.Investigate and resolve issues in diagnostic collectors that were identified by the code review:
Expand test coverage for processing of qualified names:
The text was updated successfully, but these errors were encountered: