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

Merge bloom core into doorway #89

Merged
merged 32 commits into from
May 12, 2023
Merged

Merge bloom core into doorway #89

merged 32 commits into from
May 12, 2023

Conversation

ludtkemorgan
Copy link
Collaborator

@ludtkemorgan ludtkemorgan commented May 4, 2023

This pulls over the most recent commits from bloom core into Doorway

Notes:

  • This PR shows it has 31 commits, but it is really 7 commits and a couple of merge commits. Theoretically if we do a merge instead of a squash and merge on this PR we won't have this discrepancy next time we sync with bloom core.
  • I had to change the version of @types/react in the new doorway-ui-components to satisfy the compiler. This is now set to the version of @types/react that is getting pulled into public and partners, however we might run into a similar issue again if those are updated.

ludtkemorgan and others added 30 commits March 31, 2023 12:12
* fix: user export fixes

* fix: update error message alert
* feat: upgrade react to 18

* feat: upgrade cypress to 12 for public

* feat: upgrade cypress for partners

* fix: update configs

* fix: update partner cypress tests

* fix: review comments

* fix: fix flaky cypress test
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
* fix: program/preference keys length uncap

* fix: updates per pr comments
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
* feat: upgrade nextjs to 13

* fix: attempt to get cypress test working
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
 - @bloom-housing/[email protected]
* feat: removing sensative info from leasing agent

* fix: adding swagger changes

* fix: updates for tests
Bumps [cookiejar](https://github.com/bmeck/node-cookiejar) from 2.1.2 to 2.1.4.
- [Release notes](https://github.com/bmeck/node-cookiejar/releases)
- [Commits](https://github.com/bmeck/node-cookiejar/commits)

---
updated-dependencies:
- dependency-name: cookiejar
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix: updates around cookies

* fix: creating new migration for token -> code
…oom-housing#3408)

* fix: pass proper value to to_tsquery function

* fix: search applications using ILIKE

* fix: change where to orWhere

* feat: add application search by confirmation code
* feat: updates proxy to support access control allow list

* fix: remove downstream access-control-allow-origin

* fix: update readme for m1

* fix: move purge call to the backend

* fix: test fix and add await

* fix: moving cache purge to helper

---------

Co-authored-by: Morgan Ludtke <[email protected]>
Co-authored-by: Yazeed Loonat <[email protected]>
@ludtkemorgan ludtkemorgan marked this pull request as ready for review May 5, 2023 15:36
@lisunshiny
Copy link

this overall lgtm i will pull down the branch and do some testing before stamping on monday ty!!

@lisunshiny
Copy link

features seem good -- couldnt' test the external listing stuff so I'll leave it to @chriscasto to take a look at that part!

@chriscasto
Copy link

Lgtm, but the 28k line yarn.lock file has quite a few conflicts that need to be resolved. @lisunshiny @ludtkemorgan Do either of you want to take a stab at it or should I just give it a go? It looks like it mostly involves stuff I don't touch so I don't want to accidentally break anything.

@ludtkemorgan
Copy link
Collaborator Author

Lgtm, but the 28k line yarn.lock file has quite a few conflicts that need to be resolved. @lisunshiny @ludtkemorgan Do either of you want to take a stab at it or should I just give it a go? It looks like it mostly involves stuff I don't touch so I don't want to accidentally break anything.

@chriscasto I can take a stab at that

@ludtkemorgan
Copy link
Collaborator Author

@chriscasto @lisunshiny I've merged the most recent changes from Doorway into this branch and resolved the conflicts. I started it up and it appears to all work. The only thing I can't test is the map since I don't have an api key. But other than that it looks good from my side. I think this is ready to merge whenever you are. Just make sure you merge with "create a merge commit" option. 🤞 that it will make it so the next merge will only have the newest commits from core

@chriscasto chriscasto merged commit e0d9bd8 into main May 12, 2023
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.

7 participants