Zones are not sorted in stage picker in planner and advanced query about backend-next

[FlandiaYingman]

Edit: The problem is the zoneIndex field. The zoneIndex of main_3 is 3 but for main_4 it is 0. However, the explicit sort() call did show the problem.

AFAICS, the new backend responds zones already sorted. The problem might be in the front-end. After I commented out these lines (line 175-177) in src/utils/getters.js, everything goes right:

    zones = zones.slice()
//      .sort((a, b) => {    <-  commented out these 3 lines
//        return a.zoneIndex - b.zoneIndex
//      })
      .map(el => {
        const toMerge = {}
        if (el.isActivity) {
          const existence = el.existence[server]

          if (!existence.openTime && !existence.closeTime) {
            toMerge.isPermanentOpen = true
          } else {
            toMerge.activityActiveTime = formatter.dates([existence.openTime, existence.closeTime])
            toMerge.activityStartDate = formatter.date(existence.openTime, true)
            toMerge.timeValid = formatter.checkTimeValid(existence.openTime, existence.closeTime)
            toMerge.isOutdated = toMerge.timeValid !== 0
          }
        }
        return {
          ...el,
          ...toMerge
        }
      }

[AlvISsReimu]

fixed by adjusting index column in zone table