8a0beee808
What do I mean by pivoting? Netx is currently organized by row:
```
| dialer | quicdialer | resolver | ...
saving | | | | ...
errorwrapping | | | | ...
logging | | | | ...
mocking/sys | | | | ...
```
Every row needs to implement saving, errorwrapping, logging, mocking (or
adapting to the system or to some underlying library).
This causes cross package dependencies and, in turn, complexity. For
example, we need the `trace` package for supporting saving.
And `dialer`, `quickdialer`, et al. need to depend on such a package.
The same goes for errorwrapping.
This arrangement further complicates testing. For example, I am
currently working on https://github.com/ooni/probe/issues/1505 and
I realize it need to repeat integration tests in multiple places.
Let's say instead we pivot the above matrix as follows:
```
| saving | errorwrapping | logging | ...
dialer | | | | ...
quicdialer | | | | ...
logging | | | | ...
mocking/sys | | | | ...
...
```
In this way, now every row contains everything related to a specific
action to perform. We can now share code without relying on extra
support packages. What's more, we can write tests and, judding from
the way in which things are made, it seems we only need integration
testing in `errorwrapping` because it's where data quality matters
whereas, in all other cases, unit testing is fine.
I am going, therefore, to proceed with these changes and "pivot"
`netx`. Hopefully, it won't be too painful.
|
||
|---|---|---|
| .. | ||
| atomicx | ||
| bytecounter | ||
| cmd | ||
| engine | ||
| fsx | ||
| humanize | ||
| iox | ||
| kvstore | ||
| mlablocate | ||
| mlablocatev2 | ||
| multierror | ||
| netxlite | ||
| ooapi | ||
| platform | ||
| ptx | ||
| randx | ||
| runtimex | ||
| scrubber | ||
| shellx | ||
| tunnel | ||
| tutorial | ||
| version | ||
| README.md | ||
Directory github.com/ooni/probe-cli/internal
This directory contains private Go packages.