|
@AndresFreundTec | |||||
|
I only wish it allowed negative patterns to move individual directories (e.g. tests) to the end, without having to list everything else.
|
||||||
|
||||||
|
Andres Freund (Tech)
@AndresFreundTec
|
5. lis |
|
Random useful developer discovery for postgres development: git's diff.orderFile option. Allows to change the order in which different files appear in diffs.
|
||
|
|
||
|
Andres Freund (Tech)
@AndresFreundTec
|
5. lis |
|
I've now set that to
src/include/*
src/common/*
src/port/*
config/*
src/makefiles/*
src/template/*
src/backend/*
src/fe_utils/*
src/bin/*
src/interfaces/libpq/*
src/pl/*
contrib/*
src/interfaces/*
doc/*
src/test/*
allowing me to see the "most crucial" (for me) things first.
|
||
|
|
||
|
Marius Davidsen
@MariusTweeting
|
6. lis |
|
Why would you move tests to the end? Wouldn’t the context of going through the tests along with what they test, make it faster/less context switching?
|
||
|
|
||
|
Andres Freund (Tech)
@AndresFreundTec
|
6. lis |
|
The tests I'm talking about here are integration tests, and they're in a separate directory anyway. And their output tends to often be verbose.
When reviewing code changes I try to understand the "architecture" of the change first, and tests don't help me much with that.
|
||
|
|
||