I think I went too far with my previous refactor and am backing out of it. Adding a private readBranchConfig method on the client wasn't providing any real additional value, so I've put it back into ReadBranchConfig. However, I think there is still value in having parseBranchConfig (formerly createBranchConfig) as a separate util function, as it both improves readability of ReadBranchConfig and makes parsing its purpose easier through the bespoke tests for it. |
||
|---|---|---|
| .. | ||
| fixtures | ||
| client.go | ||
| client_test.go | ||
| command.go | ||
| errors.go | ||
| objects.go | ||
| url.go | ||
| url_test.go | ||