404 error when accessing a custom GET route about forest-express HOT 5 CLOSED

Hi @arnaudbesnier ,

I was referring to this block of code inside app.js:

fs.readdirSync('./routes').forEach((file) => {
  if (file !== '.gitkeep') {
    app.use('/forest', require('./routes/' + file));
  }
});

The app is already "using" '/forest' here, so I think defining our routes as just '/brands' instead of '/forest/brands' would work fine.

from forest-express.

Hi @bidhan-a, we'd love to help you. But we need you whole Smart Collection implementation to check that everything looks good.

It might also be one of your express project middleware that could respond 404 before hitting the custom route you created.

from forest-express.

Hello @arnaudbesnier ,

Thanks for the response. I've actually managed to resolve this issue. I was following along with the documentation on how to define a custom GET route. It mentions the following:

router.get('/forest/brands', Liana.ensureAuthenticated, function (req, res) {...})

But it doesn't work that way. It should only be

router.get('/brands', Liana.ensureAuthenticated, function (req, res) {})

because '/forest' is already defined inside app.js.

from forest-express.

Thanks @bidhan-a ! Cool to see that you made it work.

I don't really understand why the route declaration:
router.get('/forest/brands', Liana.ensureAuthenticated, function (req, res) {...})
does not work as described in the documentation.

What do you mean, saying "'/forest' is already defined inside app.js"?

from forest-express.

@bidhan-a I finally understood your point... Seems to make sense.
I didn't get that you used Lumber to generate your project.

We need to improve the doc about this.

from forest-express.