Matrix url parameters break route matching

[dbpieter]

I'm currently configuring our existing single-spa app to use layout-engine.

<single-spa-router>
  <application name="navigation"></application>

  <route path="some-mfe">
    <application name="some-mfe"></application>
  </route>
</single-spa-router>

When navigating to mydomain.com/some-mfe I see the app being bootstrapped and briefly appearing. However as soon as any matrix parameters are added to the url (ex mydomain.com/some-mfe;pageSize=50;pageNumber=8) the app is unmounted by single-spa. Matrix parameters are commonly used in Angular as routing parameters.
It seems that the route matching algorithm/regex doesn't like the semicolon ?

[filoxo]

correct, because matrix url parameters aren't an accepted web standard regardless of Angular's usage so support hasn't been added. a URL with them ends up including them in the pathname which I find unexpected but makes sense since they have nowhere else to go. however, i would think it would be relatively easy to support them in matchRoute.js which has an accompanying suite of tests. would the criteria be that those URL params are ignored during matching, just like search params are?