Skip to content

fix(aci): camelCase action data fields in serializer#104597

Merged
ameliahsu merged 2 commits intomasterfrom
mia/aci/camelcase-fallthrough
Dec 9, 2025
Merged

fix(aci): camelCase action data fields in serializer#104597
ameliahsu merged 2 commits intomasterfrom
mia/aci/camelcase-fallthrough

Conversation

@ameliahsu
Copy link
Copy Markdown
Contributor

@ameliahsu ameliahsu commented Dec 9, 2025

we already made the fix to convert the action config fields to camelCase in the action serializer, so we should do the same for the data fields

@ameliahsu ameliahsu requested a review from a team as a code owner December 9, 2025 18:58
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Dec 9, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented Dec 9, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@             Coverage Diff              @@
##           master   #104597       +/-   ##
============================================
+ Coverage   68.80%    80.51%   +11.70%     
============================================
  Files        9345      9355       +10     
  Lines      400314    401035      +721     
  Branches    25741     25741               
============================================
+ Hits       275454    322892    +47438     
+ Misses     124410     77693    -46717     
  Partials      450       450               

@ameliahsu ameliahsu merged commit e419988 into master Dec 9, 2025
67 checks passed
@ameliahsu ameliahsu deleted the mia/aci/camelcase-fallthrough branch December 9, 2025 19:55
@github-actions github-actions bot locked and limited conversation to collaborators Dec 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants