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
If an extra comma , is present in use of a taglib tag, it is flagged as a syntax error by IDEA, but seems to be ignored by gsp compiler, causing the remaining attributes of the tag to be silently dropped.
e.g. we had <g:message code="by.you", default="by you"/> (note extra comma after code attribute) however the by.you message did not exist, but was still rendered as by.you instead of the default. The extraneous comma was the culprit.
Steps to Reproduce
Use invalid syntax <g:message code="missing.message", default="default value"/> (see extra comma)
Expected Behaviour
The gsp should not render due to invalid syntax (extra comma ,)
Actual Behaviour
The g:message tag works but ignores attributes after the comma. The text "missing.message" is displayed.
Environment Information
Operating System: macosX/linux
Grails Version: 2.5.6/3.3.5
JDK Version: 1.8
The text was updated successfully, but these errors were encountered:
If an extra comma
,
is present in use of a taglib tag, it is flagged as a syntax error by IDEA, but seems to be ignored by gsp compiler, causing the remaining attributes of the tag to be silently dropped.e.g. we had
<g:message code="by.you", default="by you"/>
(note extra comma after code attribute) however theby.you
message did not exist, but was still rendered asby.you
instead of the default. The extraneous comma was the culprit.Steps to Reproduce
<g:message code="missing.message", default="default value"/>
(see extra comma)Expected Behaviour
The gsp should not render due to invalid syntax (extra comma
,
)Actual Behaviour
The g:message tag works but ignores attributes after the comma. The text "missing.message" is displayed.
Environment Information
The text was updated successfully, but these errors were encountered: