Re: run pgindent on a regular basis / scripted manner
От | Andrew Dunstan |
---|---|
Тема | Re: run pgindent on a regular basis / scripted manner |
Дата | |
Msg-id | 9af5e9e7-b5e8-c761-33d0-453c660e8fca@dunslane.net обсуждение исходный текст |
Ответ на | Re: run pgindent on a regular basis / scripted manner (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On 2023-10-28 Sa 12:09, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.net> writes: >> Based on recent experience, where a lot koel's recent complaints seem to >> be about comments, I'd like to suggest a modest adjustment. >> First, we should provide a mode of pgindent that doesn't reflow >> comments. pg_bsd_indent has a flag for this (-nfcb), so this should be >> relatively simple. Second, koel could use that mode, so that it >> wouldn't complain about comments it thinks need to be reflowed. Of >> course, we'd fix these up with our regular pgindent runs. > Seems like a bit of a kluge. Maybe it's the right thing to do, but > I don't think we have enough data points yet to be confident that > it'd meaningfully reduce the number of breakages. > > On a more abstract level: the point of trying to maintain indent > cleanliness is so that if you modify a file and then want to run > pgindent on your own changes, you don't get incidental changes > elsewhere in the file. This solution would break that, so I'm > not sure it isn't throwing the baby out with the bathwater. Yeah, could be. cheers andrew. -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: