How to create a custom route that doesn't care of query params

[paztis]

I've test these 3 ways

"/test1": "/result"
"/test2\\?*": "/result",
"/test3(\?.*)?": "/result"

/test1 works but not /test1?xxxxx
/test2 didn't works but /test2?xxxxx works
/test3 and /test3?xxxxx works together, but it is a mess to write

I don't understand why we're forced to do it, while "/test3/:id": "/result?:id" works in all cases

Any idea ?

[Lisianthus-A]

You can use middleware.

const jsonServer = require('json-server');
const app = jsonServer.create();
const router = jsonServer.router(config.filePath);  // db.json
app.use(jsonServer.defaults());
app.use((req, res, next) => {
    req.query = {};
    next();
});
app.use(router);
app.listen(config.port, () => {
  console.log(`JSON Server is running on port: ${config.port}`);
});

[alexcroox]

@paztis did you find a way around this? Your test2 and test3 examples fail with an Uncaught exception and deleting the query params in middleware has no effect in 404 being returned it route includes query params

[alexcroox]

For now in my custom middleware I'm stripping params before they get to json-server:

req.url = req.url.split('?')[0]

[paztis]

Why are we forced to add custom middleware for so basic things ? Why the défaut management is not correctly supporting it ?