auto-linting about component HOT 14 CLOSED

+1 We could create issues automatically using the github api.

from component.

+1 for that issue magic.

from component.

@ForbesLindesay yup :D that's the plan, should be pretty cool. We could possibly even detect if they're using say .classList directly and suggest that they use the "classes" component

from component.

True, that would be neat. It'd be great if we could automatically detect jshint options were present and then execute jshint on the library, but that may be overkill.

I'd really really really love a feature that detected when global variables were being leaked and created issues for that.

from component.

that would be cool too, component/lint could house all that stuff, whatever we want really I suppose haha

from component.

It should have some way to disable the linting though...otherwise it would be really annoying sometimes.

Also this encroaches on the territory of Travis... Perhaps we should just set repositories up by default to do these things when people enable travis CI on them?

from component.

I mean in component-create or component-init

from component.

@visionmedia and @ForbesLindesay: Is anyone working on this? If not I have a script that ,while not terribly pretty, is more or less working.

component-lint 
        lint : /Users/adam/Projects/trigger-event/component.json
          ok : name
          ok : repo
          ok : main
          ok : description
        warn : keywords – are suggested

If you're interested I can work through the remainder of the spec and we should have something reasonable.

from component.

@adamsanderson cool! a command would be great too, I was thinking more of a script that works off of http://component.io/components/all and opens issues on github fixing things etc haha, but yeah a command-line tool would be great

from component.

@visionmedia ok, I'll clean it up and load in the rest of the spec.

I figure some other script could drive the command-line tool if someone wanted a github nagging bot. Are the end points for http://component.io documented anywhere?

Bonus: while writing this, I realized I never added any keywords to my component.

from component.

haha nice, I use the words from the description as well so that's usually enough but keywords dont hurt.

right now there's only http://component.io/components/search/ui for search queries and http://component.io/components/all. I'll remove the /components/ prefix soon

from component.

@visionmedia for what it's worth I put together component-lint.
Eventually, I would like it to suggest fixes for easy things (missing name, description, license, etc.), and also do some checks against the files, like warning if people are using prefixed css.

I think component-bot could even use it to open issues ;)

from component.

sweet ill have a look soon

from component.

If you have any suggestions, let me know. I haven't done much with node outside of little personal projects.

from component.