You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### TL;DR
Updated JSON field names to follow consistent snake_case convention and added backward compatibility for deprecated fields.
### What changed?
- Renamed `decodedData` to `decoded` in transaction and log responses
- Changed `indexedParams` to `indexed_params` and `nonIndexedParams` to `non_indexed_params`
- Added deprecated versions of the params fields to maintain backward compatibility
- Added swagger documentation tags to mark deprecated fields
### How to test?
1. Make API requests that fetch decoded logs and transactions
2. Verify new snake_case fields contain the expected data
3. Confirm deprecated camelCase fields still work and contain the same data
4. Check swagger documentation reflects the deprecated status of old fields
### Why make this change?
To establish consistent snake_case naming conventions across the API while ensuring existing integrations continue to work through a deprecation period.
0 commit comments