Re: pgindent vs. pgperltidy command-line arguments - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pgindent vs. pgperltidy command-line arguments
Date
Msg-id 825ec386-bce4-a280-3d39-47b049d640c7@dunslane.net
Whole thread Raw
In response to Re: pgindent vs. pgperltidy command-line arguments  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers


On 2023-06-21 We 07:35, Andrew Dunstan wrote:


On 2023-06-21 We 05:09, Peter Eisentraut wrote:
On 20.06.23 17:38, Andrew Dunstan wrote:
+1, although I wonder if we shouldn't follow pgindent's new lead
and require some argument(s).

That makes sense to me.  Here is a small update with this behavior change and associated documentation update.

I'm intending to add some of the new pgindent features to pgperltidy. Preparatory to that here's a rewrite of pgperltidy in perl - no new features yet but it does remove the hardcoded path, and requires you to pass in one or more files / directories as arguments.

Are you planning to touch pgperlcritic and pgperlsyncheck as well? 


Yeah, it would make sense to.



Here's a patch that turns all these into perl scripts.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Avoid overflow with simplehash
Next
From: Daniel Gustafsson
Date:
Subject: Re: Reducing connection overhead in pg_upgrade compat check phase