-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: update major dependencies #1589
Conversation
❌ Deploy Preview for detroit-storybook-dev failed.
|
✅ Deploy Preview for detroit-public-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for detroit-partners-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
1a9bdd6
to
10eab3d
Compare
@@ -74,6 +74,12 @@ const UnitsSummaryAmiForm = ({ | |||
[amiInfo, setAmiPercentageOptions] | |||
) | |||
|
|||
useEffect(() => { |
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 is an edge case only appearing on the cypress tests where the amiChartId is not being updated before the onChange event happens. By moving it to the useEffect we can guarantee that the order will happen correctly
@@ -0,0 +1,87 @@ | |||
import React from "react" |
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.
This file and the ones below it were accidentally missed when pulling over the refactoring commits from core. Specifically where we pulled things out of ui-components and into the corresponding packages they are used in
* feat: upgrade to node 19 and next 12 * fix: add netlify plugin * fix: add netlify plugin partners * fix: remove netlify plugins * fix: add netlify plugin to toml * Revert "fix: remove netlify plugins" This reverts commit 840b4a1. * fix: switch to node 16 * fix: update all places referencing node * Revert "fix: update all places referencing node" This reverts commit 9f13a5a. * Revert "fix: switch to node 16" This reverts commit 8acbfbe. * fix: re-installed with 18
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.
LGTM! Down to bash next week if we have time 🔌
^ spooky to me that cypress didn't see this |
Good point 👻 @emilyjablonski I revisited this after deleting node modules and reinstalling everything, and can't seem to reproduce the failed listing publish from before but without fail, the console errors show just from opening the add listing page. |
@ColinBuyck That console error is happening core as well. I created a ticket for it recently. bloom-housing#3392 |
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.
LGTM assuming Cypress test are just being being flakyyy 🫓
* feat: update major dependencies (#1589) * fix: update bull version (#1620) * 1577/download button can show and be non functional (#1621) * fix: display paper application button download when application is present * fix: hide redundant sections when data not provided * refactor: use paperMethod prop to decide if display download button * feat: uptake uic components (#1586) * fix: change reset to setValue for disableUnitsAccordion (#1628) * fix: various arabic layout fixes (#1629) * fix: run correct node version * fix: remove missed detroit-ui-components * fix: prettier fixes --------- Co-authored-by: Krzysztof Zięcina <[email protected]> Co-authored-by: Emily Jablonski <[email protected]>
This PR addresses #1591
Description
This upgrades several dependencies that have already been upgraded in core this includes:
It also accomplishes the following:
How Can This Be Tested/Reviewed?
This touches every page so it is recommended to go to every page and do a quick check. These changes are already in and have been tested so we don't have to be as thorough, but there are some changes that are unique so a quick passover is recommended.
You will need to test locally since it has to have a new deployed version of the backend
Checklist:
yarn generate:client
and/or created a migration if I made backend changes that require themReviewer Notes:
Steps to review a PR:
On Merge:
If you have one commit and message, squash. If you need each message to be applied, rebase and merge.