Skip to content
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

(feat): edit user role scope #561

Open
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

Ogollah
Copy link
Contributor

@Ogollah Ogollah commented Jan 21, 2025

Requirements

  • This PR has a title that briefly describes the work done, including the ticket number if there is a ticket.
  • My work conforms to the OpenMRS 3.0 Styleguide.
  • I checked for feature overlap with existing widgets.

Summary

What doe this PR do?

  • Add user role scope edit
  • Add next and back buttons between sections
  • Refactor date picker (range)
  • Add user role scope initial values

Screenshots

editRoleScope.webm
  • Updated video
Screencast.from.22-01-2025.11.20.35.ASUBUHI.webm

None.

Related Issue

None.

Other

None.

@Ogollah Ogollah requested a review from makombe January 21, 2025 13:49
@ojwanganto
Copy link
Contributor

ojwanganto commented Jan 21, 2025

@patryllus @makombe - how best can we fully qualify the inventory location and the enable and permanent settings? They look hanging and may not be straightforward to any new user.

image

  1. Should we explicitly call the location section Inventory location?
  2. The section with the enable and permanent fields can be something like Inventory user or something related. What do you think?

@Ogollah Ogollah force-pushed the feat-edit-user-role-scope branch from a93b96f to dd9e30c Compare January 22, 2025 08:52
@Ogollah Ogollah force-pushed the feat-edit-user-role-scope branch from cc7612b to 5650cd0 Compare January 22, 2025 13:39
@Ogollah Ogollah requested a review from donaldkibet January 22, 2025 14:52
@ojwanganto
Copy link
Contributor

@donaldkibet are we good to go on this?

limit?: number | null;
}

export function toQueryParams<T extends ResourceFilterCriteria>(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need to introduce this here, we can easy just specify the rest representation we want. IMO the community has always preferred to use the actual representation needed for most endpoints and we should stick to that convention

@Ogollah Ogollah force-pushed the feat-edit-user-role-scope branch from 11f6cdb to 113d352 Compare January 27, 2025 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants