cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse <purplecabb...@gmail.com>
Subject Re: [Proposal] Cordova guidelines part of ContributorWorkflow
Date Thu, 24 Apr 2014 21:22:10 GMT
I agree that jshint is awesome and powerful, I use it all the time, and so
should you.
That seems like a great end to this discussion ...
Otherwise, how do we address the 50% of our code that is not JS?

@purplecabbage
risingj.com


On Thu, Apr 24, 2014 at 2:15 PM, Martin Gonzalez Glez <
martin.c.glez.glez@gmail.com> wrote:

> jshint is really cool. Agree, +1 for jshint.
>
> A couple of questions about this, which are gonna be the validation rules?
> I mean, we have to be in the same page about which are gonna be those
> rules.
> Besides, how the users are going to use it? First they need to have the
> node module installed, and then, use a set of validation rules that we are
> going to provide?
>
> How it's gonna be? use a .jshintrc file with all the rules, general rules
> provided by the community, or each cordova component would contain a
> jshintConfig/package.json with specific validation rules. CLI+rules,
> platforms + rules, plugins + rules
> It's gonna be optional(recommended)or as requirement to deliver code, the
> usage of jshint before commit files? the contributors would need send any
> evidence, that proves that their code has passed the validation?
> Any thoughts?
>
> Jshint, it's awesome and a really good solution, I really like it.
>
> -Martin.
>
>
> 2014-04-24 10:55 GMT-05:00 Marcel Kinard <cmarcelk@gmail.com>:
>
> > Big +1 for jshint.
> >
> > On Apr 23, 2014, at 5:53 PM, Brian LeRoux <b@brian.io> wrote:
> >
> > > This may get rotten eggs thrown at me but I think it would be good to
> add
> > > jshint to the project.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message