Repository navigation
Reject commas in FastAPI and FastMCP tracing exclusions - #417
Merged
Merged
Conversation
Closes #393 Breaking changes: FastAPIConfig and FastMcpConfig now reject exclusion regexes containing commas at construction.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #393.
FastAPI and FastMCP pass exclusions to OpenTelemetry as comma-separated strings. Reject entries containing commas at config construction and identify the offending regex. Litestar receives a list and continues to honor comma-containing patterns.
Breaking changes
FastAPIConfig and FastMcpConfig now raise ConfigurationError at construction for comma-containing OpenTelemetry exclusion patterns.
Verification