What's the difference between path plus `/` in routing?

when defining routes:

const routes = [{
  path: "/",
  meta: {
    title: ""
  },
  component: (resolve) => require(["./views/index.vue"], resolve)
  children: [
    {
      path: "/a",
      name: "a",
      title:"a",
      component: (resolve) => require(["./views/a.vue"], resolve)
    },
    {
      path: "b",
      name: "b",
      title:"b",
      component: (resolve) => require(["./views/b.vue"], resolve)
    },

  ]
}];

look at the path, in children here. I"ve seen some / and some don"t. Such as path:" / a" and path:"b" above.

is there any difference in this?

Mar.02,2021

for those above you, / a and a , / b and b are all the same
assuming that your top layer is / t , then a equates to / tshock a , while / a is / a .

you didn't read the official documents carefully, did you?

Note that nested paths that start with / are treated as root paths. This allows you to make full use of nested components without setting nested paths.
MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1be8511-30632.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1be8511-30632.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?