-
Notifications
You must be signed in to change notification settings - Fork 150
chore: update build job to include multiple major react versions #7125
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
base: main
Are you sure you want to change the base?
chore: update build job to include multiple major react versions #7125
Conversation
✅ Deploy Preview for carbon-for-ibm-products ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for ibm-products-web-components ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7125 +/- ##
==========================================
- Coverage 84.45% 83.31% -1.14%
==========================================
Files 425 425
Lines 17232 17239 +7
Branches 4564 4557 -7
==========================================
- Hits 14553 14363 -190
- Misses 2679 2876 +197
🚀 New features to boost your workflow:
|
update: the action appears to be working as intended, but unfortunately the tests are failing. i'm currently investigating getting the tests to pass in v17 |
this should be ready to review. there's a lot of file changes, but the bulk of it is just to test files to add i added |
Hey @davidmenendez The test is failing in createFullpage and some merge conflicts. Could you take a look? |
code coverage dropped, but it's necessary at the moment until we can fix a lot of these flaky tests. |
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.
Code looks good to me 🎉
Please open a separate ticket for code coverage.
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.
There are a lot of .skip
s that have been added. Do we still need them?
@matthewgallo i'm going to add a followup issue to address this. but basically there's some issue with async functionality between the major test versions. rather then try to hunt down the problematic code on this PR i decided to just skip it for now. |
...mponents/FilterPanel/FilterPanelCheckboxWithOverflow/FilterPanelCheckboxWithOverflow.test.js
Outdated
Show resolved
Hide resolved
title, | ||
tooltipAlign, | ||
...rest | ||
} = props; |
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.
More of a question, I've seen this change across a handful of components, how come you've moved the prop destructuring to inside the component?
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.
i find this pattern to be useful because you can easily log all the props before separating them. it also declutters the function signature a bit.
packages/ibm-products/src/components/CoachmarkStack/CoachmarkStackHome.tsx
Outdated
Show resolved
Hide resolved
packages/ibm-products/src/components/CoachmarkStack/CoachmarkStackHome.tsx
Outdated
Show resolved
Hide resolved
- name: Add React version ${{ matrix.react }} | ||
run: | | ||
yarn add react@${{ matrix.react }} react-dom@${{ matrix.react }} | ||
yarn workspace @carbon/ibm-cloud-cognitive-core add react@${{ matrix.react }} react-dom@${{ matrix.react }} -D |
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.
yarn workspace @carbon/ibm-cloud-cognitive-core add react@${{ matrix.react }} react-dom@${{ matrix.react }} -D | |
yarn workspace @carbon/ibm-products add react@${{ matrix.react }} react-dom@${{ matrix.react }} -D |
yarn workspace @carbon/ibm-cloud-cognitive-core add @carbon/react@^1.28.0 -D | ||
yarn workspace @carbon/ibm-products add @carbon/react@^1.28.0 -P |
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.
Do you need both of these lines? Probably just the second, right? packages/core
isn't really used for anything now.
Also, how come you're installing 1.28.0
?
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.
yeah good call now that core has been decoupled.
1.28
if i remember correctly i think this version didn't include a bug that was added in a subsequent 1.x
version. this PR has been sitting around for a while so i wish i could remember the specifics of why up top, but i remember there was a specific reason
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.
hmm looks like core still needs to be included or something breaks. this might need to be looked at separately
Closes #7044 & #7137
adds a new job for testing other major versions of React. since we are currently on v18 i didn't think it made sense to include
18
in the matrix, but if we wanted to be extra safe we could also include it[17, 18]