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 the GetTraces function to return a QueryResult type instead of a raw array of traces.
### What changed?
- Modified the GetTraces function signature to return `QueryResult[common.Trace]` instead of `[]common.Trace`
- Extracted trace scanning logic into a separate `scanTrace` function
- Updated the GetTraces implementation to use the generic `executeQuery` function
- Updated the mock storage interface to reflect the new return type
### How to test?
1. Verify that existing trace queries continue to work as expected
2. Ensure that pagination and filtering functionality works correctly with traces
3. Confirm that the mock storage interface is properly implemented in test cases
### Why make this change?
This change brings consistency to the codebase by making the GetTraces function return the same QueryResult type as other query functions. This enables better pagination support and maintains a uniform interface across all data retrieval methods.
0 commit comments