title: Express route parameters vs HTTP query parameters
body: <p>I had always been wondering what kind of notation is the following,</p>
  <p><code>GET /user/:name/books/:title</code></p>
  <p>and how to interpret it until recently, when I learned that they are in the form of Express route and the ones with <code>&quot;:&quot;</code> are Express route parameters.</p>
  <p>So here comes the question that I didn't find the answers from, say,</p>
  <ul>
  <li><a href="https://stackoverflow.com/questions/27218770/">Express Route (Optional parameters)</a></li>
  <li><a href="https://stackoverflow.com/questions/34136788/">Express default route parameter</a></li>
  </ul>
  <p>The question is, what if most or even all parameters are optional? How to handle that with Express route?</p>
  <p>The problem is, with HTTP query parameters, like</p>
  <p><code>https://example.org/?page=2&amp;limit=3&amp;sort=price</code></p>
  <p>The order of query parameters can be arbitrary, whereas for Express route it seems to me the route parameters has to be specified in a very rigid way/order. So what if all route parameters are optional, and I just need to specify the last one? (no matter how you arrange the route parameters orders, there will always be a last one)</p>
  <p>I did learn that Express can deal with <code>querystring.parse(parsedUrl.query)</code>, but the reason I'm asking this question is really because of this -- <a href="https://github.com/gofiber/docs/blob/master/original/routing.md#parameters" rel="nofollow noreferrer">https://github.com/gofiber/docs/blob/master/original/routing.md#parameters</a></p>
  <p>I.e., gofiber follows/uses Express routing convention to handle route parameters, and I need all route parameters to be optional.</p>
  <p>How to deal with that?</p>