Skip to content

Dynamic Resources 404 when using nested paths #650

Open
@zackify

Description

@zackify

Describe the bug

 new ResourceTemplate("screenshot://zach.codes/{path}", { list: undefined }),

If i register a resource like this, and i pass in "test" as the path, it works correctly.

If I pass in a nested path, like "test/test" then it will not invoke my resource handler, and respond with a 404

Expected behavior

I would expect a catch all path support when registering resources.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions