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 autoformat your code and write it
in any style that appears comfortable to you. It would be useful for
someone to explore this and comment back on results.
We should be wasting less time on the appearance of code - making sure it
adheres to standards - and instead focusing on the contents of its code.
On Wed, Oct 14, 2015 at 9:39 AM, Tim Landscheidt <tim(a)tim-landscheidt.de>
wrote:
dinar qurbanov <qdinar(a)gmail.com> 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 commit
(patch set) uploads, but only automatically prettified/standartised
at/before actual commit/merge?
and, by the way, i think, should not they even be
saved as they are
written and should not, instead, diff tools automatically standartise
them before calculating difference?
How would it help the reviewer if they constantly need to
switch their mind from "prettified" code to "whatever" when
they review your code?
If you don't want to press the space bar, you can always in-
tegrate stylize
(
http://git.wikimedia.org/blob/mediawiki%2Ftools%2Fcode-utils.git/master/sty…
)
in your workflow or amend your editor to insert the spaces
when you type.
Tim
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Jon Robson
*
http://jonrobson.me.uk
*
https://www.facebook.com/jonrobson
* @rakugojon