-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New modules logger
, errfmt
and environment
#4113
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@AlonZivony do you think this would help with #4111 matter? I ask since I know this will increase maintenance efforts for both ends. Decoupling in modules can be a start to move them to repos if the respective codebase demands it anyway. |
A few thoughts:
Maybe we should remove the error handling from within the environment package and let the caller handle any returned errors? |
We should not have. I agree that converging them is the best approach to us. But we have to have in mind that splitting should avoid cyclic import issues.
If modules, bring them up to avoid cyclic import issues.
No, but it can be part of a converged module, like
Well, this is an option too. |
We are choosing another approach. #4129 |
Part of #4111 solution.
1. Explain what the PR does
1122db1 chore: use environment module
6ee5a54 chore: mv pkg/utils/environment into environment mod
4e7c7de chore: use errfmt module
efae8e6 chore: move pkg/errfmt into errfmt module
0e22c48 chore: use logger module
c211422 chore: move pkg/logger into logger module
2. Explain how to test it
3. Other comments
Well, there's no straight way of doing this relocation. So, after this merge will have at least 2 more PRs to point to the right modules hashes.