Re: run pgindent on a regular basis / scripted manner
От | Jelte Fennema |
---|---|
Тема | Re: run pgindent on a regular basis / scripted manner |
Дата | |
Msg-id | CAGECzQTGVef30yn=Yvs+dVWoOR2X0b2oLbrJxo36-3tyn1VnOQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: run pgindent on a regular basis / scripted manner (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: run pgindent on a regular basis / scripted manner
|
Список | pgsql-hackers |
On Sun, 12 Feb 2023 at 15:16, Andrew Dunstan <andrew@dunslane.net> wrote: > I'm not sure how much more I really want to do here. Given the way pgindent now processes command line arguments, maybethe best thing is for people to use that. Use of git aliases can help. Something like these for example > > > [alias] > > dirty = diff --name-only --diff-filter=ACMU -- . > staged = diff --name-only --cached --diff-filter=ACMU -- . > dstaged = diff --name-only --diff-filter=ACMU HEAD -- . > > > and then you could do > > pgindent `git dirty` > > > The only danger would be if there were no dirty files. Maybe we need a switch to inhibit using the current directory ifthere are no command line files. > > > Thoughts? I think indenting staged or dirty files is probably the most common operation that people want to do with pgindent. So I think that having dedicated flags makes sense. I agree that it's not strictly necessary and git aliases help a lot. But the git aliases require you to set them up. To me making the most common operation as easy as possible to do, seems worth the few extra lines to pgindent. Sidenote: You mentioned untracked files in another email. I think that the --dirty flag should probably also include untracked files. A command to do so is: git ls-files --others --exclude-standard
В списке pgsql-hackers по дате отправления: