You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, we can have small network and log packages.
Two benefits:
Clarity. Better to avoid ambiguous package names like common, utils, pkg, etc.
Dependency management. A user may depend on a package that only uses utils/log and utils/network, but that user will have the full utils package compiled into the binary.
The text was updated successfully, but these errors were encountered:
I would also be in favour of this, and think it's also relevant for the final point in the refactoring PR
"Extract common types from the feeder package and rpc package to the utils package to reduce duplication."
@joshklop I am happy to split the utils package into multiple sub-packages. It might be better to have them as a separate package at the root level. I don't have a strong opinion on either one
For example, we can have small
network
andlog
packages.Two benefits:
common
,utils
,pkg
, etc.utils/log
andutils/network
, but that user will have the fullutils
package compiled into the binary.The text was updated successfully, but these errors were encountered: