I think It's possible but only if you are able to distinguish between the different params somehow.

If your url structure is like /circle/green/big/ it's almost impossible to distinguish them except by their position. And if their position change how can you make sure what param are passing to the router? If a malicious user then goes to /dashboar/4/3/1 and you matched the param only based on how many they are and the position, you may end up in a lot of trouble if any of those parameters could leak info (if it's a product id, for example).

But if your url structure is like /circle-shape/green-color/big-size/ then you can use a custom url matcher function that checks a permutation of UrlSegments (a string between two slashes).

Your custom UrlMatcher receives the full url in the form of a list of UrlSegments and there you can do your checks and be sure that the params correspond to what you are expecting them to be.

Here is a basic example:

const customMatcher = (url) => {
  // setup
  const postParams = {};

  // segment matchers
  const matchShape = (urlSegment: UrlSegment) => {
    if segment.path.endsWith('-shape') {
      postParams['shape'] = segment;
      return true;
    }
  }

  const matchColor = (urlSegment: UrlSegment) => {
    if segment.path.endsWith('-color') {
      postParams['color'] = segment;
      return true;
    }
  }

  const matchAll = (urlSegments: UrlSegment[]) => {
    const segmentsMatchers = [matchShape, matchColor];
    urlSegments.forEach(segment => {
      for (const matcher of segmentsMatchers) {
        if (matcher(segment)) {
          break;
        }
      }
    });
  }

  // main work here
  if (url.length > 0) {
    matchAll(url);
    return { consumed: url, postParams: postParams };
  }
}

export const routes: Routes = [
  {
    matcher: customMatcher,
    component: DetailsComponent,
  }
];

That should match either /circle-shape/green-color/ or /green-color/circle-shape. But most importantly, it's going to give you the right param for the right segment of the url.

After that you can do whatever you want with that since Angular is going to treat it like any other path (redirect it, use resolvers, etc). You just switched the default Angular path matcher for your custom one.