More tests for source code formatting on 'master' (sql and js)

Subject: More tests for source code formatting on 'master' (sql and js)

From: Erik Huelsmann <..hidden..>

Date: Wed, 8 Jun 2016 11:09:10 +0200

Hi all,

Until today, Pg-database.sql contained "valid" tabs (as in: intentional tabs). However, since my editor is set to eliminate all tabs on save, it would have destroyed Pg-database.sql the next time I would have edited it.

In order to prevent that from happening, I've prevent this from happening, I've replaced the "valid" tabs with another delimiter. While at it, I've replaced all tabs and trailing spaces in all SQL sources, to make the files comply with the same source formatting we apply to our Perl code.

When I was done, I moved on to our JS sources as well -- we only have very little JS code at the moment, so that was easily adapted.

To prevent non-conforming code changes from entering the code base, I've implemented two new tests:

* t/01-sql-checks.t

* t/01-js-checks.t

Which at the moment simply check for trailing whitespace and tabs.

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.

------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e