lsp4jakarta
lsp4jakarta copied to clipboard
Implementations of interfaces should be allowed for Validation annotations
Description:
I noticed this with CharSequence, but there may be others. The Validation spec uses CharSequence as a type for validation because it covers String, StringBuffer, StringBuilder, and others. Anywhere the spec allows CharSequence we should allow its implementing types.
In some cases, such as @DecimalMax which allows CharSequence, we are currently indicating that String is not a valid Type for the annotation, even though it is.
Specification:
Jakarta Validation
Type of language feature proposed:
Select all that apply
- [x] diagnostic
- [ ] quick-fix
- [ ] snippet
- [ ] other, please specify:
This should be added for Jakarta EE 11