-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PIMS-680/1294: Admin Users View UI & Access Request Submission #2168
Conversation
…tation, could be improved to avoid redundant 401s when requesting without the bearer loaded.
…mented an authrouteguard to make sure the necessary context is available before making authenticated calls and rendering pages
… fetching data within react components. Included some example usage for the DevZone.
… some basic data formatters
…o work with windows (hopefully)
…ct itself from the db, plus some context/hook to use this in the frontend
…e basic flow of adding a user/access request
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like the addition of the formatters.
A few changes requested, plus linting to take care of some missing newlines.
Edit: Oops. Didn't realize this was still in draft!
…so that you can now modify user fields
…he currently logged in user.
…e pending required fields
…lete vlue for the first time'
…PIMS into PIMS-680-AdminUsersViewUI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One suggestion for how the Roles are presented, but if we're getting this from the API in the future, shouldn't be an issue. May have to adjust the enum string value though.
Believe the container issue is fixed.
options={[ | ||
//TODO: Get these through a lookup endpoint. | ||
{ label: 'Active', value: 'Active' }, | ||
{ label: 'OnHold', value: 'OnHold' }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor readable change.
{ label: 'OnHold', value: 'OnHold' }, | |
{ label: 'On Hold', value: 'OnHold' }, |
…o PIMS-680-AdminUsersViewUI
🎯 Summary
PIMS-680
Not wired up to the API in this state, for that I need 1260 merged in.
Was also considering making the form bits into their own reusable component, but I'm not sure how generic one could make it. I feel like there's usually a lot of customization that needs to be done in terms of how the fields are placed, what types of field to use, what labels to use, so much so that a reusable component might be more cumbersome than just dropping in the field components into a grid as I've done here. Any thoughts on this?
PIMS-1294
Now you should be able to submit an access request! Except there is no access request table anymore, this just creates a user with status "OnHold."
🔰 Checklist