Skip to content

[REQ] [typescript-fetch] useSingleRequestParameter should mark parameter optional if all properties are optional  #11112

Description

@davidgamero

Is your feature request related to a problem? Please describe.

when useSingleRequestParameter has all optional parameters, an empty object still has to be passed producing myApiCall({})

Describe the solution you'd like

Functions with all optional parameters should include a default empty object parameter to make it optional instead of myApiCall({})

When the default is in place, we can instead use myApiCall()

See #6477 and related #6440

Describe alternatives you've considered

Instead of making the parameter object itself optional, we can use the solution employed in the referenced PR to default which will effectively make it optional too

Additional context

Activity

  1. gambtho commented on Dec 14, 2021

    @gambtho

    resolves a problem we were having also, thanks @davidgamero

  2. Marcus-Hines commented on Dec 14, 2021

    @Marcus-Hines

    I would love to see this change made.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions