Assign to special query parameter "_path" to change path
Description
The work in https://folio-org.atlassian.net/browse/STRIPES-452#icft=STRIPES-452 allows a module to transition to another page by assigning a value into an anointed stripes-connect resource, typically called query. But that only allows us to change the query parameters of the URL, not its path.
This means that, while modules like ui-users can use this mechanism to implement searching, sorting, etc (which are all expressed in the URL query), when we need to change the path – for example to select a full record to view – we are still using direct called to history.push.
(Let the record show that Jason is unhappy about this because he has now decided that the whole https://folio-org.atlassian.net/browse/STRIPES-452#icft=STRIPES-452 approach is wrong after all. I will leave it for him to file a separate issue on why he thinks this, and what he thinks should be done about it.)
The work in https://folio-org.atlassian.net/browse/STRIPES-452#icft=STRIPES-452 allows a module to transition to another page by assigning a value into an anointed stripes-connect resource, typically called
query. But that only allows us to change the query parameters of the URL, not its path.This means that, while modules like ui-users can use this mechanism to implement searching, sorting, etc (which are all expressed in the URL query), when we need to change the path – for example to select a full record to view – we are still using direct called to
history.push.We will extend the https://folio-org.atlassian.net/browse/STRIPES-452#icft=STRIPES-452 mechanism so that assignment to the special parameter
_pathsets the path.(Let the record show that Jason is unhappy about this because he has now decided that the whole https://folio-org.atlassian.net/browse/STRIPES-452#icft=STRIPES-452 approach is wrong after all. I will leave it for him to file a separate issue on why he thinks this, and what he thinks should be done about it.)