Add parameter support to routes via naming convention
(Breaking change for any dynamic routes that currently have underscores in their names.)
Dynamic route names are parsed according to the following convention:
- One underscore becomes:
/:
- Two underscores become:
/
So, for example, to get the following route:
/people/:personId/books/:bookId
You would create the following file:
people/index_personId__books_bookId.js