Skip to content

Conversation

@mjfaga
Copy link
Collaborator

@mjfaga mjfaga commented Nov 29, 2025

No description provided.

contexts instanceof Map ? contexts : contextObjToMap(contexts);
}

get telemetry(): Telemetry | undefined {
Copy link
Collaborator Author

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?

Copy link
Contributor

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 {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. expose this?

Copy link
Contributor

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.

Comment on lines +94 to +99
withContext(contexts: Contexts | ContextObj): ReforgeInterface {
const mergedContexts = mergeContexts(this.context, contexts);
return new ReforgeClient(this.parent, mergedContexts);
}

inContext<T>(
Copy link
Collaborator Author

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?

Copy link
Contributor

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.

Copy link
Collaborator Author

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.

@mjfaga mjfaga force-pushed the mfaga-update-sdk-api branch from 0ef2f5f to 6057612 Compare November 29, 2025 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants