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
The usual conventions are that messages overflow at 73 (72 is the maximum), but this parser only has them overflowing at 74. I suspect that the issue is due to the regex for SUMMARY allowing up to 72 characters but still being preceded by NOT_A_COMMENT, which includes an additional character. Additionally, note that while the subject line overflows at 51, SUBJECT only allows for 49 characters (presumably because it also is preceded by a NOT_A_COMMENT).
Since these appear to be the only places that NOT_A_COMMENT is used, I believe that it would make sense to remove it altogether and include the [^#] directly in SUMMARY and SUBJECT. Alternatively, there may be a way to have it check whether a # is present without consuming it, although I'm not familiar enough with tree-sitter to know.
The text was updated successfully, but these errors were encountered:
The usual conventions are that messages overflow at 73 (72 is the maximum), but this parser only has them overflowing at 74. I suspect that the issue is due to the regex for
SUMMARY
allowing up to 72 characters but still being preceded byNOT_A_COMMENT
, which includes an additional character. Additionally, note that while the subject line overflows at 51,SUBJECT
only allows for 49 characters (presumably because it also is preceded by aNOT_A_COMMENT
).Since these appear to be the only places that
NOT_A_COMMENT
is used, I believe that it would make sense to remove it altogether and include the[^#]
directly inSUMMARY
andSUBJECT
. Alternatively, there may be a way to have it check whether a#
is present without consuming it, although I'm not familiar enough with tree-sitter to know.The text was updated successfully, but these errors were encountered: