-
Notifications
You must be signed in to change notification settings - Fork 0
refactor: improve public interface + don't expose resolver #37
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
base: main
Are you sure you want to change the base?
Conversation
| contexts instanceof Map ? contexts : contextObjToMap(contexts); | ||
| } | ||
|
|
||
| get telemetry(): Telemetry | undefined { |
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.
Does this actually need to be exposed?
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.
the only reason i could see exposing this is when debugging telemetry or wanting to force a flush. I think that probably means it ought not be exposed.
| }); | ||
| } | ||
|
|
||
| getLogLevel(loggerName: string): LogLevel { |
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.
Same here. expose this?
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.
seems wrong that it isn't accepting an optional context like shouldLog. It seems reasonable to be able to ask "what is log level?" as a variation of shouldLog, but I'm ok removing until someone asks.
| withContext(contexts: Contexts | ContextObj): ReforgeInterface { | ||
| const mergedContexts = mergeContexts(this.context, contexts); | ||
| return new ReforgeClient(this.parent, mergedContexts); | ||
| } | ||
|
|
||
| inContext<T>( |
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.
Do we want to support both of these?
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 don't have a strong enough opinion here about what would be most useful across various node setups.
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.
OK - I'll think about it and will probably pull one out.
0ef2f5f to
6057612
Compare
No description provided.