Skip to content

Incorrect parsing of a paginated API response when the data node contains JsonValueKind.Null #507

Description

@Jericho

While working on #506 I faced a situation where the response contained the JSON node for the data but this node contained JsonValueKind.Null. As far as I know, the JSON in the response normally omits the data node completely when there is no data and the logic in the AsPaginatedResponse<T> extension method was designed around the node being missing. The logic does not handle a null value in this field.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugThis change resolves a defect

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions