Duplicate of https://folio-org.atlassian.net/browse/STRIPES-91#icft=STRIPES-91.

Having discussed with Jason, it is now apparent that which I thought https://folio-org.atlassian.net/browse/STRIPES-91#icft=STRIPES-91 was about (allowing Stripes Connect to see the query parameter parts of the UI URL) is already in place – we think those parameters are available via the props of routed components. Instead it turns out that https://folio-org.atlassian.net/browse/STRIPES-91#icft=STRIPES-91 is about passing query parameters to the Okapi URI. In other words, it's the same issue as this one, so I am closing this as a duplicate.

It's not 100% clear what the syntax should look like for placeholders in query parameters. If we just use the same :name syntax that we use in path components, yielding manifest entries like /users/?query=:query then is that too lax? Might we for some reason want a literal : in the query part of a URL?

Anyway, as a first pass, it probably suffices just to blindly substitute any sequence of the form /:([a-z0-9])+/ with the named parameter from the UI URL.

Note that this issue is the mirror image of https://folio-org.atlassian.net/browse/STRIPES-91#icft=STRIPES-91: that one is about extending Stripes Connect so that it can ingest query parameters from the UI URL; this one is about extending it so it can emit them in WSAPI URLs.