We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a structure is created shorthand, where the last element has a trailing comma:
foo = { bar = 1, baz = 2, };
(which seems to work fine in Railo and is commonly supported by other languages), this triggers a number of parsing errors:
<issue severity="ERROR" id="PARSE_ERROR" message="PARSE_ERROR" category="CFLint" abbrev="PE"> <location file="C:\Inbox\cflint-test\.\test.cfc" fileName="test.cfc" function="" column="2" line="7" message="Unable to parse" variable=""> <Expression><![CDATA[no viable alternative at input '{\r\n\t\t bar=1,\r\n\t\t baz=2,\r\n\t\t}']]></Expression> </location> </issue> <issue severity="ERROR" id="MISSING_SEMI" message="MISSING_SEMI" category="CFLint" abbrev="MS"> <location file="C:\Inbox\cflint-test\.\test.cfc" fileName="test.cfc" function="" column="13" line="5" message="End of statement(;) expected instead of ," variable=""> <Expression><![CDATA[,]]></Expression> </location> </issue> <issue severity="ERROR" id="MISSING_SEMI" message="MISSING_SEMI" category="CFLint" abbrev="MS"> <location file="C:\Inbox\cflint-test\.\test.cfc" fileName="test.cfc" function="" column="13" line="6" message="End of statement(;) expected instead of ," variable=""> <Expression><![CDATA[,]]></Expression> </location> </issue>
The same applies with nested structures. There will be similar errors reported when this is scanned:
var foo = { bar = 1, baz = { foo = 2, } };
The text was updated successfully, but these errors were encountered:
https://github.com/cflint/CFLint/issues/263
dbfc4b1
fixed in cfparser 2.4.5
Sorry, something went wrong.
No branches or pull requests
When a structure is created shorthand, where the last element has a trailing comma:
(which seems to work fine in Railo and is commonly supported by other languages), this triggers a number of parsing errors:
The same applies with nested structures. There will be similar errors reported when this is scanned:
The text was updated successfully, but these errors were encountered: