-
Notifications
You must be signed in to change notification settings - Fork 84
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
Warnings for non-existing errors and non-lint errors before output. #105
Comments
fixed in master |
In the fix you want to return 1 not 0 if element doesn't exist, otherwise the line number can be off by one. |
Thanks for thinking about that Justin. I did double check and it's getting On Fri, Oct 16, 2015 at 3:04 AM, Justin Mclean [email protected]
|
Well, returning 1 reports the correct line number in my case as well. On Fri, Oct 16, 2015 at 6:25 AM, Ryan Eberly [email protected] wrote:
|
For example see the new name rule stuff I've checked in,all nine of the script tests will fail if the method returns zero. It also makes sense that the first line in a file is 1 not 0 - well to me anyway. :-) |
Sounds good to me. thanks, On Fri, Oct 16, 2015 at 7:03 AM, Justin Mclean [email protected]
|
It's working now. Thanks a lot! |
When linting an extremely simple cfc errors stating: "Message code: is not configured correctly." come up.
It then proceeds to mark valid lines of code as warnings with no message, id, or abbrev.
CFLint Version: 0.5.1-SNAPSHOT
master branch.
Note: the error messages do not output to files, only to the command line. Therefore I'm attaching a picture of the screen output as well as files generated by cflint and the code of the CFC.
tick.cfc:
Text version:
Strange thing is that it doesn't happen with every file, just some of them and I haven't been able to figure out why.
The text was updated successfully, but these errors were encountered: