QueryString handling

[firedev]

Nice and clean. Do you plan to have a way of handing query string?

[Paratron]

This is an interesting suggestion! I would not use it for the routing itself tough, but make the query/GET params available in the result function.

For example, if you have this URL: /section/plushies?order=asc, I would have the route processed like this:

const routes = {
    '/section/:sectionName': ({sectionName}, {order}) => <RenderSection name={sectionName} sortOrder={order} />
};

Having a second argument passed to the result function would not break the existing API.

[arvinsingla]

This is the exact question I was going to ask and the exact answer I was hoping to hear. Hope you’ll consider adding this. This project looks awesome!

Edit: just realized you tagged this as “Done(to be released)” yay!!

[Paratron]

Released with 1.1.0.

Can be used with the useQueryParams() hook, which returns [queryParams, setQueryParams]. Its completely object based and automatically serialized/deserialized. Docs to follow.