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

UICAL-285 - Disable 'Actions' menu on DCB Calendar. #535

Merged
merged 5 commits into from
Sep 30, 2024

Conversation

Terala-Priyanka
Copy link
Contributor

@Terala-Priyanka Terala-Priyanka commented Sep 28, 2024

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.

  • I've added an appropriate record to the CHANGELOG.md
  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?

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.

@Terala-Priyanka Terala-Priyanka marked this pull request as draft September 28, 2024 06:27
Copy link

github-actions bot commented Sep 28, 2024

Jest Unit Test Statistics

    1 files  +    1    73 suites  +73   2m 36s ⏱️ + 2m 36s
332 tests +332  331 ✔️ +331  1 💤 +1  0 ±0 
359 runs  +359  358 ✔️ +358  1 💤 +1  0 ±0 

Results for commit 4108ca1. ± Comparison against base commit eb8122a.

♻️ This comment has been updated with latest results.

@Terala-Priyanka Terala-Priyanka marked this pull request as ready for review September 28, 2024 06:57
@Terala-Priyanka Terala-Priyanka requested a review from a team September 28, 2024 06:58
@Terala-Priyanka Terala-Priyanka self-assigned this Sep 28, 2024
Copy link
Member

@ncovercash ncovercash left a 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?

// await userEvent.click(screen.getByRole('button', { name: 'Actions' }));
// });

// expect(screen.getByRole('button', { name: 'Edit' })).toBeInTheDocument();
Copy link
Member

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?

Copy link
Contributor Author

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

Copy link

@Terala-Priyanka
Copy link
Contributor Author

Should there be any changes in mod-calendar to protect this calendar from manipulation via API?

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

@Terala-Priyanka Terala-Priyanka merged commit 66afcdf into master Sep 30, 2024
5 checks passed
@Terala-Priyanka Terala-Priyanka deleted the UICAL-285 branch September 30, 2024 05:40
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