[FOLIO-853] Regression of ui-user dependencies "permissions" and "login" Created: 25/Sep/17  Updated: 12/Nov/18  Resolved: 25/Sep/17

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: Mike Taylor Assignee: Mike Taylor
Resolution: Cannot Reproduce Votes: 0
Labels: sprint23
Remaining Estimate: Not Specified
Time Spent: 1 hour
Original estimate: Not Specified

Issue links:
Relates
relates to UIU-172 rewire permissions and credentials ha... Closed
Sprint:

 Description   

The ui-users module depends on several back-end module interfaces, including permissions 5.0 and login 4.0, both as of 12 September: https://github.com/folio-org/ui-users/commit/774b36f9bd116e4c8b7a68a97cc859e71d32aeb3

But having just updated my folio/testing-backend VM to the most recent version, v5.0.0-20170925.158), I find from the Stripes About page that it only provides the previous major versions of both of these interfaces: permissions 3.0 and permissions 4.0.



 Comments   
Comment by Mike Taylor [ 25/Sep/17 ]

Matt Connolly, what was the trigger for updating the dependcies in ui-users' package.json? Was it related to a Jira issue?

Wayne Schneider, is seems that the most recent VM doesn't give us the versions of these modules that we need: is it possible that there's a regression in the build process?

Comment by Matt Connolly [ 25/Sep/17 ]

Mike Taylor Yes, permissions 5 and login 4 are the first interfaces that require identification by ID rather than username.

Comment by Mike Taylor [ 25/Sep/17 ]

All right – so this is going to be a breaking change, and we will need the new permissions and login modules released and included in the backend VM ASAP. Correct?

Comment by Matt Connolly [ 25/Sep/17 ]

Yes — but they were there before, in the builds from about 10 days ago. Kurt, Wayne, and I coordinated this very carefully so that it wouldn't be an issue. Could be a regression, like you said.

Comment by Mike Taylor [ 25/Sep/17 ]

OK, we wait for Wayne Schneider to wake up and comment.

Comment by Mike Taylor [ 25/Sep/17 ]

Panic over. It's a bit feeble, really.

Reloading Stripes fixes this.

I guess I was still seeing the old Stripes session's previously-loaded Okapi metadata, back from when I was running v4.something of the backend VM.

Generated at Thu Feb 08 23:08:48 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.