Insufficient warning that routes are potentially merged too, when merging areas

[killakalle]

Probably a bit of an edge case, but I wanted to point it out anyhow.

While restructuring an area, I accidentally merged routes that should not have been merged.

How did it happen?

When you are merging areas, there is this big red warning box that informs you about the dangers of merging. In addition it always lists all the routes that are going to be moved over. So far so good, but that is actually the happy flow and is expected.

However, when there are two routes in both sectors with the same name, then it will also merge the routes. In my opinion, that is quite uncommon, and should be pointed out to the user separately. However, because there is always the big red warning box, this bit of information is easily missed as you stop reading the contents after a while of restructuring areas.

When can this case happen?

Probably rare, because it only affects areas where there are duplicate route names. You probably don't want to merge routes, when there are a lot of unknown route names, e.g. SN1, SN2, SN3, in both sectors.

Expected:

• Better highlighting of the unusual case when area merging also merges routes.