Skip to content

fix(allowed-domains): preserve blank origin values - #129428

Draft
joshuarli wants to merge 1 commit into
getsentry:masterfrom
joshuarli:fix/origin-blank-value
Draft

joshuarli wants to merge 1 commit into
getsentry:masterfrom
joshuarli:fix/origin-blank-value

Conversation

@joshuarli

@joshuarli joshuarli commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

Behavioral split from #129431.

OriginField coerced a blank origin to None after validation, so callers saw a different value than the one submitted. Preserve the empty string and leave empty-value filtering to the storage layer.

Test: test_blank_origin_is_preserved.

A blank origin was coerced to None after field validation, so callers
saw a different value than the one submitted. Keep the empty string and
let downstream empty-value filtering decide what to store.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant