-
Notifications
You must be signed in to change notification settings - Fork 85
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
Docs for using linter via java #12
Comments
Is at as simple as linter.getBugs()? |
Hmm. If I run getBugList on it, I get a struct based on the type of error, and then arrays in there. That works, but is there a way to get list as is, in the order found? I can easily convert a struct of arrays into one array, but just asking if there is something baked in. |
Hmm. I didn't put much thought into making it a friendly java API to You can get an array of arrays with which isn't much a simplification over struct of arrays. On Wed, Jul 30, 2014 at 3:09 PM, Raymond Camden [email protected]
|
i just mandhandled it myself. Want a copy of the extension before I blog it? On Wed, Jul 30, 2014 at 3:41 PM, ryaneberly [email protected]
Raymond Camden, Web Developer for Adobe Email : [email protected] |
Great, glad you were able to roll it out. I don't have a local CFBuilder On Wed, Jul 30, 2014 at 4:54 PM, Raymond Camden [email protected]
|
Forgot to mention: On Wed, Jul 30, 2014 at 7:34 PM, Ryan Eberly [email protected] wrote:
|
Ok, I'll blog it tomorrow. On Wed, Jul 30, 2014 at 6:34 PM, ryaneberly [email protected]
Raymond Camden, Web Developer for Adobe Email : [email protected] |
I enhanced the API to include a progress monitor, but you have to explicitly ask for it. linter = createObject("java","com.cflint.CFLint"); And added It will be available in the next version. |
Less a bug and more a request for help. Given that I've got an instance of the linter, and I see there is a scan API:
linter = createObject("java","com.cflint.CFLint");
linter.scan(selection.path);
But it returns void. How do I get the results?
The text was updated successfully, but these errors were encountered: