Skip to content

client: Verify path parameters are non-empty before sending request #122

@bmoylan

Description

@bmoylan

@ungureanuvladvictor had an issue that was hard to debug where a generated client was receiving 404s because a path parameter was provided as the empty string to a path like /service/api/path/{param} so it rendered as /service/api/path/

Possible solution: Add a precondition before sending a request that all path parameters are non-empty.

@iamdanfox @ferozco does Java deal with this? Any edge cases where empty would be correct?

cc @nmiyake

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