Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of purplecabbage@gmail.com
 designates 74.125.82.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CBDABBF9.6746%fil@adobe.com>
References: 
 <CACAoQH1iYdWKKNe4QONnuh-eyDsTHzpj=hd+==4ffPnQ6nyepA@mail.gmail.com>
	<CBDABBF9.6746%fil@adobe.com>
Date: Thu, 17 May 2012 14:43:10 -0700
Message-ID: 
 <CAKP6k2sC3SUVfLA8+xPC4Kp_8SogjkPacqQW5eEvxtL02ny5NQ@mail.gmail.com>
Subject: Re: jshint and white-space "fixes"
From: Jesse <purplecabbage@gmail.com>
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e6d5900972462204c04252ff

--0016e6d5900972462204c04252ff
Content-Type: text/plain; charset=ISO-8859-1

+1, I mentioned this to Fil a while ago, but he was being anal that day.
Personally, I think the builder should just build, and the Linter should
just lint, but having Linting built into the builder is non-destructive,
and informational only, so I can live with it.


On Thu, May 17, 2012 at 2:32 PM, Filip Maj <fil@adobe.com> wrote:

> K I get that. So let's change it to only complain and not re-write tabs.
> And trailing white space if that applies here.
>
> Also, srsly, run the tests/a build before you push commits. Comeon folks
> (I'm looking at you Mr. Bada!)
>
> On 5/17/12 2:16 PM, "Patrick Mueller" <pmuellr@gmail.com> wrote:
>
> >> "why you gotta do this to me pat?" [1]
> >
> >jshint didn't complain to me at all, even though it seems to be running as
> >part of every build. [2]  What am I doing wrong?
> >
> >That seems weird, because in, fact, I >did< see whitespace fixes in that
> >bada file (that you "fixed" in your commit), AFTER I had done a build.
> > Because the white-space-fixer DOES run as part of the build [3]. Of
> >course, I didn't make any changes to the bada file, so was a little
> >confused it showed up as a mod in git status. (I reverted it before I did
> >my commit, so my "fixed" version was not committed).
> >
> >It seems wrong to have the white-space-fixer run like that.  I don't mind
> >it COMPLAINING about a file with "wrong" whitespace during a "build".  I
> >DO
> >NOT LIKE that it rewrites source code during a "build".
> >
> >The fact that a bada file with "bad whitespace" ended up committed means
> >someone didn't do a build after changing the file, sometime before it was
> >committed, since the evil white-space-fixer-behind-your-back woulda fixed
> >it up.  >THAT< is a problem.
> >
> >[1]
> >
> http://git-wip-us.apache.org/repos/asf?p=incubator-cordova-js.git;a=commit
> >;h=b1673e3e
> >[2]
> >https://github.com/apache/incubator-cordova-js/blob/master/Jakefile#L60
> >[3]
> >https://github.com/apache/incubator-cordova-js/blob/master/Jakefile#L101
> >
> >--
> >Patrick Mueller
> >http://muellerware.org
>
>


-- 
@purplecabbage
risingj.com

--0016e6d5900972462204c04252ff--