Skip to content

Add tools to help discover ambiguous routes #50

Open
@Firehed

Description

@Firehed

The current matching system (and any regexp-based matching system in general) can allow you to create routes, and there is no defined behavior for what order the matches will be attempted in (in practice; it's loosely based on whatever order find returns files in).

Some loose heuristic would be to look for all test cases that use the EndpointTestTrait, combine all of their goodUris() into a list, and test for good uris that match against multiple endpoints. This can get really complicated across different request methods today, and would get even more complex should disambiguation across other request variants (e.g. accept headers).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions