fix(aci): Snake casing for data sources in evidence data #103858
Merged
Conversation
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
github-actions
bot
added
the
Scope: Backend
scttcper
approved these changes
Nov 21, 2025
malwilley
deleted the
malwilley/fix/snake-casing-for-data-sources-in-evidence-data
branch
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.
I missed this in #103549
I was using the default serializer, which outputs camelcased keys. However, the occurrence evidence data uses snake case by convention. Using camelcased keys also has a problem where our event detail endpoint will run a camel-case converter again, which does things like
snubaQuery -> snubaqueryand then the frontend can't reuse those types.So this runs the serialized data source through a casing converter to ensure it's snake case.