Skip to content
This repository was archived by the owner on Oct 8, 2018. It is now read-only.
This repository was archived by the owner on Oct 8, 2018. It is now read-only.

Convention-based endpoint resolution should consider QueryString parameters #3

@Rychard

Description

@Rychard

When resolving an endpoint, the parameters are not considered at all. Only after a endpoint is resolved are the QueryString parameters accessed, at which point we are unable to redirect the invocation.

Here are some notes regarding this:

  • Endpoint resolution should consider the parameters of a method.
  • At minimum, we must consider parameters that are required.
  • Considering the Type of parameter would introduce a lot of complexity, as it would lead to the suggestion of supporting complex-type binding. For now, let's keep it simple.
  • Like ASP.NET, throw exceptions when resolution fails.

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