Integrate @folio/requests into running system

Description

has created this module, but has been having trouble getting it included in a runnin Stripes system.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Mike Taylor July 17, 2017 at 11:56 AM

Closing this. , if you have any more problems, feel free to ping me directly.

Mike Taylor July 17, 2017 at 11:54 AM

Annoyingly, it turns out that the routing problem is also due to the missing permission. The routes get established once, when Stripes starts up, at which point you don't have the permission. Then you give yourself the permission using the console (or by turning on "Act as though user has all permissions?" in *Settings -> Developer -> Configuration") and the Requests icon appears; but by then, the routes have already been established and /requests is not among them.

In the short term, the simplest fix is to add hasAllPerms: true to the config section of your stripes.config.js file. In the long term – as soon as we get a new folio/testing-backend VM built using the updated Requests package-file – all you'll need to do is add the new permission to the user you want to run as.

Mike Taylor July 17, 2017 at 10:52 AM

Next problem: when you click on the Requests icon, you get: "Uh-oh! This route does not exist." I don't yet know why this is.

BTW., this is not fixed just by removing the home entry from the package file, which is almost certainly not needed here, and it just left over from a copy-pasted Users package file.

Mike Taylor July 17, 2017 at 10:01 AM

(BTW., I moved this issue from STRIPES to UIREQ because, while I initially thought the problem was with the set of steps required to get a module integrated, it turned out to be a specific issue with ui-requests,)

Mike Taylor July 17, 2017 at 10:00 AM

Clearly this is not a good long-term solution

Step 1 is to add the module.requests.enabled permission to the package file, so that that permission is included in the available set going forward. I have done this: https://github.com/folio-org/ui-requests/commit/491a0f58715fd71c06f05bb6fae369c755984c1c

So once you are running against a back-end box that has been built with the new ui-requests, the necessary permission will be available for Diku Admin to add to itself (or any other user).

Wayne, life would become simpler if this permission were in the set that is initially assigned to Diku Admin. Can you please make it so?

Done

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 17, 2017 at 9:16 AM
Updated June 8, 2020 at 2:18 AM
Resolved July 17, 2017 at 11:56 AM
TestRail: Cases
TestRail: Runs