How do you prevent two people from configuring the same predicates path, but different downstream services lead to one person routing not working?

How do you prevent two people from configuring the same predicates path, but different downstream services lead to one person routing not working?
Such as：
route1:

spring:
  cloud:
    gateway:
      routes:
      - id: route1
        uri: http://123.book.com
        predicates:
        - Path=/book/**
        filters:
        - RewritePath=/book/(?<segment>.*), /$\{segment}

route2:

spring:
  cloud:
    gateway:
      routes:
      - id: route2
        uri: http://456.book.com
        predicates:
        - Path=/book/**
        filters:
        - RewritePath=/book/(?<segment>.*), /$\{segment}

The above configuration comes from two people who don't know each other.It can result in a certain person's configuration invalid.
How do you prevent this, such as giving friendly reminders or reporting errors directly when the same path configuration is saving? Is the spring cloud gateway supported?

No source file or test is named. Start by reviewing Spring Cloud Gateway's route predicate matching and route configuration behavior against the two Path=/book/** examples; a complete issue would need a decided validation or conflict-handling requirement and a reproducer.