-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Deprecate all types and funcs in config package #6422
Deprecate all types and funcs in config package #6422
Conversation
Codecov ReportBase: 91.64% // Head: 91.86% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #6422 +/- ##
==========================================
+ Coverage 91.64% 91.86% +0.22%
==========================================
Files 238 238
Lines 13811 13616 -195
==========================================
- Hits 12657 12509 -148
+ Misses 924 878 -46
+ Partials 230 229 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
6f2fe5e
to
bee1ea8
Compare
/cc @dmitryax since I remember you also mentioned this to me |
This seems like a good solution to me. I was thinking about taking a similar approach. |
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.
Still working through reviewing the changes, overall i think this makes sense. Will this change (once the deprecated funcs are removed) completely decouple config
from component
?
bee1ea8
to
ea54801
Compare
@codeboten @dmitryax PTAL |
0e5bded
to
0a8f738
Compare
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.
Overall LGTM
Please rebase
798755c
to
7ef05a3
Compare
Done. |
967dc86
to
c2fd7b9
Compare
0d78abd
to
59948fc
Compare
The main reason is to remove the circular dependency between the config (including sub-packages) and component. Here is the current state: * component depends on config * config/sub-package[grpc, http, etc.] depends on config & component Because of this "circular" dependency, we cannot split for example "config" into its own module, only if all the other config sub-packages are also split. Signed-off-by: Bogdan <bogdandrutu@gmail.com>
Signed-off-by: Bogdan <bogdandrutu@gmail.com>
59948fc
to
dd19a00
Compare
Signed-off-by: Bogdan <bogdandrutu@gmail.com>
dd19a00
to
74e53c9
Compare
The main reason is to remove the circular dependency between the config (including sub-packages) and component. Here is the current state:
Because of this "circular" dependency, we cannot split for example "config" into its own module, only if all the other config sub-packages are also split.
Updates #6187