Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of purplecabbage@gmail.com
 designates 209.85.128.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANOW_pAOLzDdbOtBe1PKh95cRwES=K=wEZie8OxW8tw53=8-jQ@mail.gmail.com>
References: 
 <CANOW_pCh49-aPxS05nx3K+p96Ndv1X46F-1bU3vF5RvcEcUNpg@mail.gmail.com>
	<CAE6O_-aToc6-PZYZ5cfFDHiAXtzpDgLQnpUj25dz01Wir=0v6w@mail.gmail.com>
	<CA+GVa3amuaRbvMaCwwVyaPzvSy0nsW6EdrSUf-FgBPtNWJM6wA@mail.gmail.com>
	<CABiQX1V=NFZWgP3-srftP_1zy3MuKkd8oxeLRSaa4pRkwZ+pxg@mail.gmail.com>
	<CAKP6k2sKPewXchqQgwMDocUFXs7qdt7TpdxEk_gqRkhC5QnaiA@mail.gmail.com>
	<CANOW_pDB33ZODitJY9bG1SU4p5pwd8=1a16ewvKdUkEo0rHLmw@mail.gmail.com>
	<CADVgkyMYwqUVarahVwyFfm5mwrQEzCkkTpB2D8Wbi4eeTm-cTQ@mail.gmail.com>
	<DC6EDFBA-FBCF-494E-996C-40FA0748D48C@gmail.com>
	<CANOW_pAOLzDdbOtBe1PKh95cRwES=K=wEZie8OxW8tw53=8-jQ@mail.gmail.com>
Date: Thu, 24 Apr 2014 14:22:10 -0700
Message-ID: 
 <CAKP6k2tM+f2aSRfOUM0hLr_RY2-XGavwPRSirp8f9tr2QrD=bw@mail.gmail.com>
Subject: Re: [Proposal] Cordova guidelines part of ContributorWorkflow
From: Jesse <purplecabbage@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a11c20810251e5604f7d071ca

--001a11c20810251e5604f7d071ca
Content-Type: text/plain; charset=UTF-8

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.
> >
>

--001a11c20810251e5604f7d071ca--