Don't spawn Anthropic telemetry event when API key is missing #32813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor refactor that I'm extracting from a branch because it can stand alone.
report_anthropic_eventif it's just going to immediately fail due to API key being missingreport_anthropic_eventnow takes aStringAPI key instead ofOption<String>and the error reporting if the key is missing has been moved to the caller.report_anthropic_eventis longer coupled toAnthropicError, because all it ever did was generate anAnthropicEvent::Other, which in turn was then only used forlog_err- so, can just be ananyhow::Result.Release Notes: