Comments (4)
Ease of use is important. But I don't think you want to tackle "remove dependence on Java". CF itself runs on java -- we should be able to reuse the CF java install without needing to install java somewhere else. that would make sense.
from linter-cflint.
@ryaneberly Since you maintain the CFLint project, these questions would best be directed to you. Do you see the project introducing any breaking changes? If so, would those be reserved for major version changes?
I can see the "ease of use" point, but based on the answers to the questions above I wonder if it would be possible to dynamically pull the latest compatible version then. Either way, my suggestion for storing the location as configuration remains.
from linter-cflint.
I don't see any breaking changes in the near future. the CLI interface and output have stabilized. I think it's far to expect reasonable compatibility on all future 1.x.x releases
from linter-cflint.
Following up with this:
- I found node-github-releases which seems to be under atom's organization. There's no documentation, but it looks like it might work to keep CFLint updated if its GitHub releases are kept up-to-date, which it doesn't seem that they are at the moment. I expect the ability to filter by version numbers exists as well.
- I also found an NPM CFLint wrapper, which should be easy to integrate, and while it does depend on Java, you would at least be removing the direct dependency since that seems to be one of your goals. It unfortunately doesn't add much at the moment, but if properly maintained I think letting it manage keeping CFLint updated makes more sense than in an editor plugin.
from linter-cflint.
Related Issues (20)
- On the fly linting
- Errors are not sorted by line
- Do not use execSync HOT 5
- Add tests
- Errors identified one line below actual error. HOT 1
- Allow enabling/disabling rules HOT 13
- Rewrite parser/linter in JavaScript HOT 7
- Remove need for separate download of CFLint.jar HOT 2
- Remove need for configuring Java directory
- Possible CFLint Changes HOT 3
- False warning returned - Component name source is not a valid name
- unused-method-argument doesn't pick up scoped arguments. HOT 6
- Getting registry errors when I open a .CFM file in Atom HOT 4
- An unexpected error occured with linter-cflint. See the debug log for details HOT 1
- Fresh installation (atom and cflint) HOT 2
- Unexpected error HOT 10
- unexpected error - prettier-atom HOT 1
- unable to parse HOT 2
- Unrecognized Lucee 5 'new' syntax HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from linter-cflint.