Spring Cloud Gateway MVC does not honor the route "order" attribute

Version: org.springframework.cloud:spring-cloud-starter-gateway-mvc -> 4.1.5

org.springframework.cloud.gateway.server.mvc.config.RouteProperties defines an attribute order that presumably would control the order that routes are evaluated. I would like to maintain the routes in configuration such that the route ids are in alphabetical, and in the case of overlapping predicates where order is important, use the order attribute to control evaluation order. When I tried this though, it did not work, and I had to change the physical order of the route definitions to get the correct behavior.
It appears that either the order attribute should be deprecated and it should be documented that the physical order of routes is the only way to control evaluation order, or some sorting of the routes by order should be implemented such that when the order is specified, it is honored.

This is what I would like my configuration to look like:

        - id: route-1
          order: 2
          uri: lb://service1
          predicates:
            - Path=/api/v1/resource/**
          filters:
            - RewritePath=/api/v1/resource/(?<segment>.*),/api/service1/v1/resource/$\{segment}
        - id: route-2
          order: 1
          uri: lb://service2
          predicates:
            - Path=/api/v1/resource/sub-resource/**
          filters:
            - RewritePath=/api/v1/resource/sub-resource/(?<segment>.*),/api/service2/v2/sub-resource/$\{segment}

but using this configuration all requests to /api/v1/resource/** were routed using "route-1", nothing used "route-2".

I needed to revise my configuration as follows to get the desired behavior:

        - id: route-2
          uri: lb://service2
          predicates:
            - Path=/api/v1/resource/sub-resource/**
          filters:
            - RewritePath=/api/v1/resource/sub-resource/(?<segment>.*),/api/service2/v2/sub-resource/$\{segment}
        - id: route-1
          uri: lb://service1
          predicates:
            - Path=/api/v1/resource/**
          filters:
            - RewritePath=/api/v1/resource/(?<segment>.*),/api/service1/v1/resource/$\{segment}

Start with org.springframework.cloud.gateway.server.mvc.config.RouteProperties and reproduce the two overlapping Path predicates from the issue configuration. Trace how the MVC gateway evaluates those configured routes and determine whether the order attribute is intended to control evaluation or should be deprecated and documented. Done means the behavior is resolved consistently for the supplied route pair.