-
Notifications
You must be signed in to change notification settings - Fork 130
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
Javadoc validation does not take into account implied end tags #1858
Comments
It also not seem to notice if a tag is not closed at all like here Javadoc complains:
|
jdt does not have complete javadoc validation. if you want to propose a PR ... welcome. |
more specifically: jdt validates (supposedly) all that is specific to javadoc, but it does not and probably should not validate HTML (nor markdown for that matter). IMHO, that would be a good task for an additional plugin. |
I don't see anyone planning to work on HTML validation in JDT |
See this from the spec:
https://html.spec.whatwg.org/multipage/parsing.html#closing-elements-that-have-implied-end-tags
https://github.com/eclipse-equinox/equinox/blob/392063733c664ef504c8c46006633df98955a463/bundles/org.eclipse.equinox.bidi/src/org/eclipse/equinox/bidi/internal/StructuredTextDelimsEsc.java#L24-L34
the
<p>
tag is implicitly closed, but JDT does not complain but javadoc does when it sees another closing tag:this currently make it quite hard to spot errors like this ones:
The text was updated successfully, but these errors were encountered: