Skip to content

OBPIH-6837 TD: Install second react table package#4972

Merged
awalkowiak merged 1 commit intodevelopfrom
OBPIH-6837
Dec 12, 2024
Merged

OBPIH-6837 TD: Install second react table package#4972
awalkowiak merged 1 commit intodevelopfrom
OBPIH-6837

Conversation

@alannadolny
Copy link
Collaborator

✨ Description of Change

A concise summary of what is being changed. Please provide enough context for reviewers to be able to understand the change and why it is necessary. If the issue/ticket already provides enough information, you can put "See ticket" as the description.

Link to GitHub issue or Jira ticket: https://pihemr.atlassian.net/browse/OBPIH-6837

Description: Because of the changes in packages in a newer version of react table I didn't have to use a forked library as a replacement for react-table version 6. I was able to add the newest version of the library and I tested it and it worked fine. The example that I tried to run in the app: https://tanstack.com/table/v8/docs/framework/react/examples/basic


📷 Screenshots & Recordings (optional)

If this PR contains a UI change, consider adding one or more screenshots here or link to a screen recording to help reviewers visualize the change. Otherwise, you can remove this section.
image

@alannadolny alannadolny self-assigned this Dec 5, 2024
@github-actions github-actions bot added the flag: config change Hilights a pull request that contains a change to the app config label Dec 5, 2024
@codecov
Copy link

codecov bot commented Dec 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 7.61%. Comparing base (c6b8d10) to head (096dd76).
Report is 130 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff              @@
##             develop   #4972      +/-   ##
============================================
- Coverage       7.65%   7.61%   -0.05%     
+ Complexity       825     817       -8     
============================================
  Files            601     601              
  Lines          42302   42302              
  Branches       10276   10276              
============================================
- Hits            3239    3222      -17     
- Misses         38593   38612      +19     
+ Partials         470     468       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

"@fortawesome/free-solid-svg-icons": "5.14.0",
"@fortawesome/react-fontawesome": "0.1.8",
"@hookform/resolvers": "3.3.4",
"@tanstack/react-table": "8.20.5",
Copy link
Member

Choose a reason for hiding this comment

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

is the plan to replace line 104 "react-table": "6.8.6", with this? Or do they work independently?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, we want to replace it in the future, but it will probably be in the far-distant future. For now, we would like to have those libraries independently, the new library includes a new "hook" approach which will be needed in the cycle count implementation.

Copy link
Member

Choose a reason for hiding this comment

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

sounds good. It's convenient that we can bring in both versions at the same time and then gradually switch over to using this new dependency.

My main concern is around having to support different behaviours across different tables, which may lead to inconsistencies in our UI, but I don't know the react table library well enough to know if that's a real concern or not.

Either way we'd probably need this upgrade eventually, so good that we're starting now

@awalkowiak awalkowiak added warn: do not merge Marks a pull request that is not yet ready to be merged and removed warn: do not merge Marks a pull request that is not yet ready to be merged labels Dec 9, 2024
@awalkowiak awalkowiak merged commit 24f1487 into develop Dec 12, 2024
@awalkowiak awalkowiak deleted the OBPIH-6837 branch December 12, 2024 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flag: config change Hilights a pull request that contains a change to the app config

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants