>If you really want to rewrite MW's coding style to your own, you could
>probably get away with a post-checkout hook in your git repo. That would
>let you look at MW code with all the ugly spaces removed :)
i do not think that spaces after commas is not beautiful or not easy
to read, but i used to
On 10/14/2015 10:53 PM, Jon Robson wrote:
> FYI if you are talking about JavaScript you might want to explore
> http://jsbeautifier.org/
Yes. And if you are using an IDE(Example: atom), there are extensions
that will beautify
your code as per a defined jsbeautify configuration on file save or
manua
On Wed, Oct 14, 2015 at 10:23 AM, Jon Robson wrote:
> All code standards are currently being enforced by jscs.
> They recently closed an issue to add auto-formatting
> https://github.com/jscs-dev/node-jscs/issues/516
There's also the --fix flag to jscs, which automatically fixes
whitespace-only
dinar qurbanov wrote:
>> How would it help the reviewer if they constantly need to
>> switch their mind from "prettified" code to "whatever" when
>> they review your code?
> it is possible to show prettified code in gerrit web pages, and send
> prettified version to people if they get it via git
On Wed, Oct 14, 2015 at 11:57 AM dinar qurbanov wrote:
> >Apologies for the bluntness, but if you cannot conform to the coding
> standards of a project in terms of minor things such as spacing, how can we
> know or trust you that you are confirming to standards that are more
> meaningful, such as
On Wed, Oct 14, 2015 at 12:07 PM, Gergo Tisza wrote:
> On Wed, Oct 14, 2015 at 10:42 AM, dinar qurbanov wrote:
>
> > it is possible to show prettified code in gerrit web pages, and send
> > prettified version to people if they get it via git fetch, but save
> > also their original form .
Also
On Wed, Oct 14, 2015 at 10:42 AM, dinar qurbanov wrote:
> it is possible to show prettified code in gerrit web pages, and send
> prettified version to people if they get it via git fetch, but save
> also their original form .
>
It really isn't.
___
Wik
>Apologies for the bluntness, but if you cannot conform to the coding standards
>of a project in terms of minor things such as spacing, how can we know or
>trust you that you are confirming to standards that are more meaningful, such
>as those related to security? ...
we are talking about chang
Apologies for the bluntness, but if you cannot conform to the coding standards
of a project in terms of minor things such as spacing, how can we know or trust
you that you are confirming to standards that are more meaningful, such as
those related to security?
Standards allow for a consistent a
> How would it help the reviewer if they constantly need to
> switch their mind from "prettified" code to "whatever" when
> they review your code?
it is possible to show prettified code in gerrit web pages, and send
prettified version to people if they get it via git fetch, but save
also their ori
FYI if you are talking about JavaScript you might want to explore
http://jsbeautifier.org/
All code standards are currently being enforced by jscs.
They recently closed an issue to add auto-formatting
https://github.com/jscs-dev/node-jscs/issues/516
In theory, you could create a script to autoform
dinar qurbanov wrote:
> i think i lose my individuality and that i have to make extra key
> presses to set extra spaces near brackets and commas. currently tests
> / automatical reviews show in gerrit that my commit has such errors.
> what if they are not (would not be? were not? ) blamed on comm
i think i lose my individuality and that i have to make extra key
presses to set extra spaces near brackets and commas. currently tests
/ automatical reviews show in gerrit that my commit has such errors.
what if they are not (would not be? were not? ) blamed on commit
(patch set) uploads, but only
13 matches
Mail list logo
