You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For instance, we don't want /pages/products/_product/_variant.vue to handle /products. I think this is a sane default, I can't think of many instances where the detail component also handles the listing view.
We currently handle this with something like:
# nuxt.config.coffeeexportdefault# Customize the routesrouter:extendRoutes: (routes) -># Make the slug required on these routes so the listing pages can# be towersdetailRoutes= [ 'articles-article', 'recipes-recipe' ]
for route in routes
ifroute.namein detailRoutes
thenroute.path=route.path.slice(0, -1)
For instance, we don't want
/pages/products/_product/_variant.vue
to handle/products
. I think this is a sane default, I can't think of many instances where the detail component also handles the listing view.We currently handle this with something like:
I think this functionality gets added to https://github.com/BKWLD/cloak-boilerplate/blob/master/modules/routing.js and it just removes the
?
at the end of all routes except _tower.vue so that dynamic parts are never optional.The text was updated successfully, but these errors were encountered: