Routing

Like Gatsby and NextJS, ChiselStrike routes incoming requests by matching the URL path against the endpoint-code path.

When you create a file endpoints/posts.ts, the URL /dev/posts invokes it. When you create a file endpoints/new/york/city.ts, the URL /dev/new/york/city invokes it.

When there is no exact match, ChiselStrike uses the longest prefix of the URL path that matches an existing endpoint definition. In the previous example, the URL /dev/new/york/city/manhattan/downtown will also be handled by endpoints/new/york/city.ts (assuming no other endpoints).

This routing procedure enables endpoints to handle both the 'plural' and 'single' versions of themselves.

For example, the above endpoint my-backend/endpoints/comments.ts will be invoked when you access a specific comment, eg, at /dev/comments/1234-abcd-5678-efgh. The BlogComment.crud() will parse the URL and understand that a single collection element is being accessed.