I've now also modified Items.js to use this function, and bumped its stripes-components dependency to v0.0.3.

Added to stripes-components, which I have now released as v0.0.3.

• Change-log at https://github.com/folio-org/stripes-components/blob/master/CHANGELOG.md

• Documentation at https://github.com/folio-org/stripes-components/blob/master/util/README.md

I've modified Users.js to use this function, and bumped its stripes-components dependency to v0.0.3.

Jason points out that there might be react-router facilities to do this; or it's possible even that the browser's history object supports in. But the former is subject to change and I don't want to tie us to the present 4.0beta version of react-router; and the latter is about the least browser-portable feature there is. Also, Bertrand didn't seem to know a standard way of doing what we want here.

So I am going to ignore those options for now, and we can revisit them later if we stumble across a better way to do what transitionToParams does – perhaps when upgrading to the final v4.x of react-router.

Also, we considered whether this function belongs in stripes-components, in a new stripes-utils package, or even in it's own tiny react-router-transition package. Instead of waiting around for ages, and leaving a P2 sprint9 issue open and stalled, I am just going to go ahead and shove it into stripes-components. We can always change our minds later.

This isn't complete until we've made a decision and put the utility somewhere shareable. So it will need to be discussed for the next sprint.

Jason's comment on Slack:

I think a stripes-utilities repo would be neat and I also think that it actually could be good to have multiple NPMs in there where they make sense eg. there might be a more general purpose for a javascript CQL parser / object->CQL converter