Allow multiple slugs in route segment

[JohnPeel]

Allow multiple slugs in route segment

Description

Currently you are not allowed to have multiple slugs in a single segment. (e.g. src/routes/[file].[ext].js)

This merge request relates to issue #547.

The regex used to find these parts will detect file].[ext as a slug because it is greedy.
I've made it non-greedy..

I also fixed an issue with non-dynamic parts of the segment (e.g. the . in the above filename) that are being treated as regex.

• Example: http://localhost:3000/blog/what-is-sapperajson when using the example code given on new project. (Note the "a" instead of a ".", the "." in the pattern can be any character because it is treated as regex)

Issues

• The change to sanitize non-dynamic parts of the segment may break projects that take advantage of the bug.

Changes

• Regex for getting parts from a file segement was made non-greedy.
• Added regex sanitizing to non-dynamic parts of segment.
  • This broke a few tests (e.g. . => \.), these were fixed.
• Added tests for multiple slugs (with and without nested square brackets).

Note

There is no lint script in your package.json.

---

Before submitting the PR, please make sure you do the following

• It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases features are absent for a reason.
• This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
• Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to npm run lint!)

Tests

• Run the tests tests with npm test or yarn test)