-
Notifications
You must be signed in to change notification settings - Fork 2
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
UICAL-285 - Disable 'Actions' menu on DCB Calendar. #535
Conversation
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.
Should there be any changes in mod-calendar to protect this calendar from manipulation via API?
src/views/panes/InfoPane.test.tsx
Outdated
// await userEvent.click(screen.getByRole('button', { name: 'Actions' })); | ||
// }); | ||
|
||
// expect(screen.getByRole('button', { name: 'Edit' })).toBeInTheDocument(); |
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.
Why are these commented out?
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.
Removed the commented code as it is unnecessary
Quality Gate passedIssues Measures |
BE had not implemented the change at api level for DCB calendar to not be editable. They might do it for ramsons but not for Q csp5 |
Purpose
UICAL-285 - Disable editing of DCB calendar
@folio-org/fe-tl-reviewers @ncovercash Kindly review this PR with priority as it is needed for Q CSP#5.
Approach
DCB transactions are associated with an umbrella calendar hardcoded in BE as "DCB Calendar".
The actions menu for this DCB Calendar is supposed to be hidden i.e., editing DCB Calendar is forbidden from UI.
Refs
https://folio-org.atlassian.net/browse/UICAL-285
Screenshots
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
If there are breaking changes, please STOP and consider the following:
Ideally, all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of inter-module and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.