having "hardcoded" switches for default chain configs everywhere is too complex and too redundant and leaves too many opportunities for errors and inconsistencies:
much of this is because of crufty, brittle code (inheriting code where these cases have been carelessly hardcoded with approaching infinite opinionation).
I'm not sure the best pattern for approach yet. Big global? Moar interfaces? Mmmm..
this needs improving:
https://github.com/etclabscore/multi-geth/blob/master/cmd/utils/flags.go#L1567-L1623
having "hardcoded" switches for default chain configs everywhere is too complex and too redundant and leaves too many opportunities for errors and inconsistencies:
much of this is because of crufty, brittle code (inheriting code where these cases have been carelessly hardcoded with approaching infinite opinionation).
I'm not sure the best pattern for approach yet. Big global? Moar
interface
s? Mmmm..Rel #63