allow to optionally use `file.relative` instead of `file.path` when matching about en-route HOT 3 CLOSED

By doing this it will allow us to write middleware handlers like this:

Versus what? What does it do now?

edit: also, what is the original file path versus expected?

from en-route.

fwiw, to do what you want all you have to do is:

router.onLoad('(.*)/posts/:post/:index*', (file, params) => {
  console.log(params) //=> { '0': '/path/to/files', post: 'post-1', index: 'index.hbs' }
});

edit: I started adding support for file.relative, but since checking both paths would perform the entire matching operation twice, it would definitely be slower than just prepending (.*). Maybe we can come up with an option that automatically prepends that or something.

edit2: I forgot, you should also be able to do this:

router.onLoad(':base(.*?)/posts/:post/:index*', (view, params) => {
  console.log(params);
  //=> { base: 'path/to/files', post: 'post-1', index: 'index.hbs' }
});

from en-route.

The patterns that you point out aren't something I thought of. That will work instead of adding additional support for something else. Thanks.

from en-route.