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

UISACQCOMP-168: add default columnWidths for donors list #731

Merged
merged 1 commit into from
Nov 20, 2023

Conversation

alisher-epam
Copy link
Contributor

Purpose

UISACQCOMP-168 - add columnWidths to fix column issue

Approach

Screen.Recording.2023-11-17.at.8.38.50.PM.mov

Pre-Merge Checklist

Before merging this PR, please go through the following list and take appropriate actions.

  • I've added 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 they 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 intermodule 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.

@alisher-epam alisher-epam requested review from a team and usavkov-epam November 17, 2023 15:40
Copy link

github-actions bot commented Nov 17, 2023

Jest Unit Test Statistics

    1 files  ±0  146 suites  ±0   4m 1s ⏱️ +4s
384 tests ±0  383 ✔️ ±0  1 💤 ±0  0 ±0 
386 runs  ±0  385 ✔️ ±0  1 💤 ±0  0 ±0 

Results for commit dc784c1. ± Comparison against base commit fcf089d.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Nov 17, 2023

BigTest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ±0 

Results for commit dc784c1. ± Comparison against base commit fcf089d.

♻️ This comment has been updated with latest results.

Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@alisher-epam alisher-epam merged commit fb7b054 into master Nov 20, 2023
5 checks passed
@alisher-epam alisher-epam deleted the UISACQCOMP-168 branch November 20, 2023 05:24
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