[Bug Report] Incorrect dts Generation for Nested Index Routes

[TrueNine]

Given the following file structure:

- pages/
  - index/
    - index.vue
    - ...
  - index.vue

The generated dts is as follows:

export interface RouteNamedMap {
  '/': RouteRecordInfo<'/', '/', Record<never, never>, Record<never, never>>,
  '//': RouteRecordInfo<'//', '/', Record<never, never>, Record<never, never>>,
  '//device_frame/': RouteRecordInfo<'//device_frame/', '/device_frame', Record<never, never>, Record<never, never>>,
  '//mobile/': RouteRecordInfo<'//mobile/', '/mobile', Record<never, never>, Record<never, never>>,
  '//pad/': RouteRecordInfo<'//pad/', '/pad', Record<never, never>, Record<never, never>>,
  '//pc/': RouteRecordInfo<'//pc/', '/pc', Record<never, never>, Record<never, never>>,
  '/design/home': RouteRecordInfo<'/design/home', '/design/home', Record<never, never>, Record<never, never>>,
}

Note: The appearance of double slashes (//) in the generated routes is quite confusing and unexpected, even though this may not be a common scenario.

[posva]

This is expected. As you see in your routes, you already have “/“ and “/design” that are unrelated to that route. Note this is just the name of the route and that you can put a name between parentheses instead of index: (app)/index.vue (app).vue

[TrueNine]

Thank you for your answer, I really appreciate it. My question has been resolved, and I’m grateful for your contribution to the community.