You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to Javadoc specification, tags are case-sensitive, meaning that @foo and @Foo are different tags.
Currently, Dokka treats tags in a case-insensitive manner, resolving @param, @PARAM and @pArAm into the standardized @param tag. It would be nice to follow the spec here to avoid surprising behavior.
Additionally, I've verified that IDEA's Javadoc parser also treats tags in a case-sensitive manner
The text was updated successfully, but these errors were encountered:
* Get rid of safeEnumValueOf that was an unnecessary public API burden and constantly allocating
* Restructure JavadocParser.parseDocTag so it has one lever of nesting less
* Make tag parsing case-sensitive
Fixes#2907
* Get rid of safeEnumValueOf that was an unnecessary public API burden and constantly allocating
* Restructure JavadocParser.parseDocTag, so it has one lever of nesting less
* Make tag parsing case-sensitive
Fixes#2907
According to Javadoc specification, tags are case-sensitive, meaning that
@foo
and@Foo
are different tags.Currently, Dokka treats tags in a case-insensitive manner, resolving
@param
,@PARAM
and@pArAm
into the standardized@param
tag. It would be nice to follow the spec here to avoid surprising behavior.Additionally, I've verified that IDEA's Javadoc parser also treats tags in a case-sensitive manner
The text was updated successfully, but these errors were encountered: