-
Notifications
You must be signed in to change notification settings - Fork 24
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: upgrading typeorm #3340
feat: upgrading typeorm #3340
Conversation
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for bloom-core-orm ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for bloom-partners-orm ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@YazeedLoonat Any remaining concerns post-bash yesterday? Are you looking for more partners bashing on the preview link? |
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 haven't found any functional issues, but still investigating how to solve that broken skipped test. There is a chance the AFS code has an issue, but more likely we just need to update the test somehow
@ludtkemorgan @seanmalbert @emilyjablonski @ColinBuyck this should be ready for re-review now! |
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.
🦖 🌮
@YazeedLoonat do you mind resolving the merge conflicts when you get a chance? Hoping to test this with listings export! |
hey @ColinBuyck merge conflicts have been resolved, lemme know what you think |
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.
Hey @ColinBuyck this should be good to go again |
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 🍌 I rate this 12/10!
* feat: upgrading typeorm * fix: updates for tests * fix: updating nestjs packages, clean up per morgan * fix: undoing nestjs bump * fix: missed changes * fix: minor typeorm version update * fix: user update per sean * fix: listings update per sean * fix: test updates * fix: hopefully resolves failing build on heroku * fix: attempt 2 on fixing heroku deploy * fix: updates * fix: update throttling in tests * fix: asset test fix * fix: updates for images and multiselect * fix: update for mfa * fix: type fix * fix: another type fix * fix: update for partner test * fix: issue with jurisdiction resolver service * fix: test fixes * fix: fix for mfa tests? * fix: attempt at mfa test fix * fix: remove listing service from afs cron job (bloom-housing#3428) * fix: update for tests * fix: fix for dup resolution --------- Co-authored-by: Morgan Ludtke <ludtkemorgan@gmail.com> Co-authored-by: Sean Albert <smabert@gmail.com> Co-authored-by: Morgan Ludtke <42942267+ludtkemorgan@users.noreply.github.com>
* feat: upgrading typeorm (bloom-housing#3340) * feat: upgrading typeorm * fix: updates for tests * fix: updating nestjs packages, clean up per morgan * fix: undoing nestjs bump * fix: missed changes * fix: minor typeorm version update * fix: user update per sean * fix: listings update per sean * fix: test updates * fix: hopefully resolves failing build on heroku * fix: attempt 2 on fixing heroku deploy * fix: updates * fix: update throttling in tests * fix: asset test fix * fix: updates for images and multiselect * fix: update for mfa * fix: type fix * fix: another type fix * fix: update for partner test * fix: issue with jurisdiction resolver service * fix: test fixes * fix: fix for mfa tests? * fix: attempt at mfa test fix * fix: remove listing service from afs cron job (bloom-housing#3428) * fix: update for tests * fix: fix for dup resolution --------- Co-authored-by: Morgan Ludtke <ludtkemorgan@gmail.com> Co-authored-by: Sean Albert <smabert@gmail.com> Co-authored-by: Morgan Ludtke <42942267+ludtkemorgan@users.noreply.github.com> * fix: upgrade all nest dependencies (bloom-housing#3461) * fix: add additional unit fields to base view (bloom-housing#3492) * Revert "fix: comment out income validation and change to text field (#620)" This reverts commit f56fdad. --------- Co-authored-by: Yazeed Loonat <YazeedLoonat@gmail.com> Co-authored-by: Sean Albert <smabert@gmail.com>
* feat: upgrading typeorm * fix: updates for tests * fix: updating nestjs packages, clean up per morgan * fix: undoing nestjs bump * fix: missed changes * fix: minor typeorm version update * fix: user update per sean * fix: listings update per sean * fix: test updates * fix: hopefully resolves failing build on heroku * fix: attempt 2 on fixing heroku deploy * fix: updates * fix: update throttling in tests * fix: asset test fix * fix: updates for images and multiselect * fix: update for mfa * fix: type fix * fix: another type fix * fix: update for partner test * fix: issue with jurisdiction resolver service * fix: test fixes * fix: fix for mfa tests? * fix: attempt at mfa test fix * fix: remove listing service from afs cron job (bloom-housing#3428) * fix: update for tests * fix: fix for dup resolution --------- Co-authored-by: Morgan Ludtke <ludtkemorgan@gmail.com> Co-authored-by: Sean Albert <smabert@gmail.com> Co-authored-by: Morgan Ludtke <42942267+ludtkemorgan@users.noreply.github.com>
Pull Request Template
Issue Overview
This PR addresses #issue
Description
This PR upgrades TypeORM to a much newer version
How Can This Be Tested/Reviewed?
To be honest every part of the system needs to be tested:
listings
creating, editing, viewing (public and partners)
applications
creating, editing, viewing (public and partners
users
creating, editing, viewing
duplicate listings
resolving, marking as duplicate, viewing
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.