Skip to content

Route matching should stop at first route match #17

@OKNoah

Description

@OKNoah

Currently the packages/final-server/updater.js will attempt to match all routes. This was a design mistake. Since components can already match multiple routes and methods, there's little reason to allow this, in my mind. This actually creates a big right now where the last-most route will catch provide the eventual response to a request.

If this is fixed, we can also do 404 and catch-all routes easily.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions