-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Fix circular dependency #5402
Fix circular dependency #5402
Conversation
Codecov Report
*This pull request uses carry forward flags. Click here to find out more.
|
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 -not sure if needs action but the same pattern seems to exist in node-token-validation as well
@@ -122,7 +122,7 @@ const DEFAULT_LOGGER_OPTIONS: LoggerOptions = { | |||
|
|||
const DEFAULT_SYSTEM_OPTIONS: Required<NodeSystemOptions> = { | |||
loggerOptions: DEFAULT_LOGGER_OPTIONS, | |||
networkClient: NetworkUtils.getNetworkClient(), | |||
networkClient: new HttpClient(), |
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.
I thought the initial idea was to ensure generic client setup, where setNetworkClient()
would enable them to set the specific network client.
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.
Approved. I think we already have a demo by Robbie for custom network implementation, so this looks fine.
🎉 Handy links: |
Fixes circular dependency