Skip to content

[utils] Forbid undefined values on request and response objects #10199

Description

@rekmarks

Here's the problem:

> JSON.stringify({ foo: undefined })
'{}'

Any request or response objects that are serialized before being transported will lose any fields with the value undefined. Introspecting params or errors to suss out such fields is beyond the scope of this package, but there's an argument that we should throw errors if we detect that any top-level top-level request or response property exists and has the value undefined.

That may also be out of scope for this package, but this is as good a place to track it as any.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions