Skip to content

Route parameters not supported when string value #8

Closed
@TheJayMann

Description

@TheJayMann

Attempting to generate a method which has a parameter in the route template where the parameter is defined as a string causes the parameter to be ignored completely. This appears to be caused by only considering value typed parameters (not including CancellationToken) as valid. Given that string is often used as a primitive even though it is not a value type, I believe it should be special cased in, similar to how CancellationToken is currently special cased out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions