fix: ledger_data returns an empty list (instead of null) when all entries are filtered out #4398
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.
High Level Overview of Change
This PR resolves issue 4392. When the
type
field to theledger_data
method is specified, it is possible that no objects of the specified type are found. When this happens, thestate
field of the response has the valuenull
instead of an empty array ([]).Context of Change
The PR initializes the
state
field of the response to an empty list so that the field is not anull
. This can break client code that explicitly checks fornull
. However, this behavior is consistent with the documentation.Type of Change