-
Notifications
You must be signed in to change notification settings - Fork 75
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: user resource policy allocation in user setting modal #2749
feat: user resource policy allocation in user setting modal #2749
Conversation
Your org requires the Graphite merge queue for merging into mainAdd the label “flow:merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “flow:hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @ironAiken2 and the rest of your teammates on |
Coverage report for
|
St.❔ |
Category | Percentage | Covered / Total |
---|---|---|---|
🔴 | Statements | 5.35% (-0% 🔻) |
348/6506 |
🔴 | Branches | 4.84% | 218/4503 |
🔴 | Functions | 3.12% (-0% 🔻) |
67/2150 |
🔴 | Lines | 5.24% (-0% 🔻) |
333/6356 |
Show new covered files 🐣
St.❔ |
File | Statements | Branches | Functions | Lines |
---|---|---|---|---|---|
🔴 | ... / UserResourcePolicySelector.tsx |
0% | 100% | 0% | 0% |
Test suite run success
93 tests passing in 12 suites.
Report generated by 🧪jest coverage report action from f060300
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.
LGTM. Please make another PR to display user resource policy info on the info modal.
Merge activity
|
<!-- Please precisely, concisely, and concretely describe what this PR changes, the rationale behind codes, and how it affects the users and other developers. --> This PR resolves #2727 issue. **Changes:** - The user creation modal is written as a Lit Element, so I applied it to the edit modal first. - When migrating the user creation modal to react component, I �thought that we need a user resource policy selector, so I wrote it as a separate component. - The `user_resource_policy` query doesn't provide filtering options yet, so I didn't add any filtering logic, but used antd's built-in search. **How to test:** - Verify that the existing user's resource policy is properly applied as the default value. - In the user information edit modal, verify that the user's resoure policy is modified correctly. |before|after| |---|---| |![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/lSyr8xXz1wdXALkJKzVx/e0c21f2d-a56b-4fd8-ab23-36048c46904d.png)|![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/lSyr8xXz1wdXALkJKzVx/b520b92e-be57-40dc-bd99-4ce9b04dc451.png)| **Checklist:** (if applicable) - [x] Mention to the original issue - [ ] Documentation - [ ] Minium required manager version - [ ] Specific setting for review (eg., KB link, endpoint or how to setup) - [ ] Minimum requirements to check during review - [ ] Test case(s) to demonstrate the difference of before/after
b7eac6a
to
f060300
Compare
This PR resolves #2727 issue.
Changes:
user_resource_policy
query doesn't provide filtering options yet, so I didn't add any filtering logic, but used antd's built-in search.How to test:
Checklist: (if applicable)