2022-03-10 release

.circleci/config.yml

@@ -35,8 +35,6 @@ executors:
       REDIS_TLS_URL: "rediss://localhost:6379/0"
       REDIS_URL: "redis://localhost:6379/0"
       REDIS_USE_TLS: "0"
-      CLOUDINARY_SECRET: "fake_secret"
-      CLOUDINARY_KEY: "fake_key"
       PARTNERS_PORTAL_URL: "http://localhost:3001"
   puppeteer-node:
     docker:
@@ -105,8 +103,10 @@ jobs:
             REDIS_TLS_URL: "rediss://localhost:6379/0"
             REDIS_URL: "redis://localhost:6379/0"
             REDIS_USE_TLS: "0"
-            CLOUDINARY_SECRET: "fake_secret"
+            CLOUDINARY_SIGNED_PRESET: "fake_secret"
             CLOUDINARY_KEY: "fake_key"
+            CLOUDINARY_CLOUD_NAME: "exygy"
+            CLOUDINARY_SECRET: "fake_secret"
             PARTNERS_PORTAL_URL: "http://localhost:3001"
   build-public:
     executor: standard-node
@@ -120,6 +120,12 @@ jobs:
       - restore_cache:
           key: build-cache-{{ .Environment.CIRCLE_SHA1 }}
       - run: yarn build:app:partners
+  unit-test-partners:
+    executor: standard-node
+    steps:
+      - restore_cache:
+          key: build-cache-{{ .Environment.CIRCLE_SHA1 }}
+      - run: yarn test:app:partners:unit
 
 workflows:
   version: 2
@@ -147,7 +153,11 @@ workflows:
       - build-partners:
           requires:
             - setup
+      - unit-test-partners:
+          requires:
+            - setup
       - cypress/run:
+          name: "cypress-public"
           requires:
             - setup
           executor: cypress-node
@@ -158,3 +168,15 @@ workflows:
           start: yarn dev:all-cypress
           wait-on: "http://0.0.0.0:3000"
           store_artifacts: true
+      - cypress/run:
+          name: "cypress-partners"
+          requires:
+            - setup
+          executor: cypress-node
+          working_directory: sites/partners
+          yarn: true
+          build: |
+            yarn test:backend:core:dbsetup
+          start: yarn dev:all-cypress
+          wait-on: "http://0.0.0.0:3001"
+          store_artifacts: true

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/general-issue.md

@@ -0,0 +1,26 @@
+---
+name: General Issue
+about: Issues for a feature
+title: "[Issue Title]"
+labels: ''
+assignees: ''
+
+---
+
+**What is this feature or what feature is this part of?**
+A clear and concise description of what the problem is.
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+**What is the acceptance criteria/definition of done?**
+A clear and concise description of the acceptance criteria required to close this issue.
+
+**QA Review Instructions**
+This is to be filled out by the developer who completes this issue, before passing to QA.

.github/workflows/lint.yml

@@ -1,7 +1,7 @@
 name: Lint
 
 on:
-  # Trigger the workflow on push or pull request,
+  # Trigger the workflow on pull request,
   # but only for the dev branch
   push:
     branches:

.github/workflows/pre-release_components.yml

@@ -0,0 +1,40 @@
+name: Pre-release ui-components
+
+on:
+  # Triggers the workflow on push only for the dev branch
+  push:
+    branches: [ dev ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Config user name
+        run: git config --global user.name github.context.workflow
+
+      - name: Config user email
+        run: git config --global user.email "[email protected]"
+
+      - name: Check out git repo
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.ADMIN_TOKEN }}
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v1
+        with:
+          node-version: 14
+          registry-url: 'https://registry.npmjs.org'
+
+      - name: Version ui-components
+        run: yarn version:prerelease:ui-components
+        env:
+          GITHUB_TOKEN: ${{ secrets.ADMIN_TOKEN }}
+
+      - name: Publish ui-components
+        run: yarn publish:ui-components
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.gitignore

@@ -81,6 +81,7 @@ yarn-error.log
 # IDE configs
 .idea
 .vscode
+*.code-workspace
 
 # VS code debugger config
 launch.json
@@ -90,3 +91,7 @@ test-coverage/
 
 # redis dumps
 dump.rdb
+
+# csv import files
+backend/core/detroit-listings.csv
+backend/core/detroit-listings-units.csv

.prettierignore

@@ -2,3 +2,8 @@
 .github
 .travis.yml
 ui-components/src/locales
+ui-components/CHANGELOG.md
+sites/public/CHANGELOG.md
+sites/partners/CHANGELOG.md
+shared-helpers/CHANGELOG.md
+backend/core/CHANGELOG.md

.travis.yml

@@ -35,33 +35,33 @@ jobs:
       name: "Backend e2e tests"
     - script: yarn test:public:unit-tests
       name: "Public site unit tests"
-    - stage: longer tests
-      script: yarn test:shared:ui:a11y
-      name: "Storybook a11y testing"
-    - stage: longer tests
-      name: "Public site Cypress tests"
-      script:
-        - yarn cypress install
-        - yarn db:reseed
-        - cd backend/core
-        - yarn nest start &
-        - cd ../../sites/public
-        - yarn build
-        - yarn start &
-        - yarn wait-on "http-get://localhost:3000" && yarn cypress run
-        - kill $(jobs -p) || true
-    - stage: longer tests
-      name: "Partners site Cypress tests"
-      script:
-        - yarn cypress install
-        - yarn db:reseed
-        - cd backend/core
-        - yarn nest start &
-        - cd ../../sites/partners
-        - yarn build
-        - yarn start -p 3001 &
-        - yarn wait-on "http-get://localhost:3001" && yarn cypress run
-        - kill $(jobs -p) || true
+    # - stage: longer tests
+    #   script: yarn test:shared:ui:a11y
+    #   name: "Storybook a11y testing"
+    # - stage: longer tests
+    #   name: "Public site Cypress tests"
+    #   script:
+    #     - yarn cypress install
+    #     - yarn db:reseed
+    #     - cd backend/core
+    #     - yarn nest start &
+    #     - cd ../../sites/public
+    #     - yarn build
+    #     - yarn start &
+    #     - yarn wait-on "http-get://localhost:3000" && yarn cypress run
+    #     - kill $(jobs -p) || true
+    # - stage: longer tests
+    #   name: "Partners site Cypress tests"
+    #   script:
+    #     - yarn cypress install
+    #     - yarn db:reseed
+    #     - cd backend/core
+    #     - yarn nest start &
+    #     - cd ../../sites/partners
+    #     - yarn build
+    #     - yarn start -p 3001 &
+    #     - yarn wait-on "http-get://localhost:3001" && yarn cypress run
+    #     - kill $(jobs -p) || true
 
 addons:
   postgresql: "11"

CHANGELOG.md

@@ -94,6 +94,25 @@ All notable changes to this project will be documented in this file. The format
 
 ## Unreleased
 
+## Frontend
+
+- Fixed:
+
+  - Language typo in the paper applications table ([#1965](https://github.com/bloom-housing/bloom/pull/1965)) (Jared White)
+  - Improved UX for the Building Selection Criteria drawer ([#1994](https://github.com/bloom-housing/bloom/pull/1994)) (Jared White)
+  - alternate contact email is validated ([#2035](https://github.com/bloom-housing/bloom/pull/2035)) (Yazeed)
+  - Incorrect last name ([#2107](https://github.com/bloom-housing/bloom/pull/2107)) (Dominik Barcikowski)
+
+## Backend
+
+- Fixed:
+
+  - Incorrect listing status ([#2015](https://github.com/bloom-housing/bloom/pull/2015)) (Dominik Barcikowski)
+
+## v2.0.0-pre-tailwind 09/16/2021
+
+## Frontend
+
 - Added:
 
   - Support PDF uploads or webpage links for building selection criteria ([#1893](https://github.com/bloom-housing/bloom/pull/1893)) (Jared White)
@@ -128,9 +147,12 @@ All notable changes to this project will be documented in this file. The format
   - Listings management AMI charts populate after Save and New on units ([#1952](https://github.com/bloom-housing/bloom/pull/1952)) (Emily Jablonski)
   - Brings in updates from Alameda which fixes some issues with preference handling and lisitngs getStaticProps in production ([#1958](https://github.com/bloom-housing/bloom/pull/1958))
   - Preview can load without building address ([#1960](https://github.com/bloom-housing/bloom/pull/1960)) (Emily Jablonski)
+  - Page now scrolls after closing modal ([#1962](https://github.com/bloom-housing/bloom/pull/1962)) (Emily Jablonski)
+  - Copy & New and Save & New in LM will no longer create duplicate units ([#1963](https://github.com/bloom-housing/bloom/pull/1963)) (Emily Jablonski)
 
 - Changed:
 
+  - Update text for preferred unit types and terms ([#1934](https://github.com/bloom-housing/bloom/pull/1934)) (Jared White)
   - Upgrade the public and partners sites to Next v11 and React v17 ([#1793](https://github.com/bloom-housing/bloom/pull/1793)) (Jared White)
     - **Breaking Change**
   - The main changes are around removing the try catch blocks so errors prevent the build from finishing (should cover #1618) and the export script was removed, since it isn't valid with [fallback: true](https://nextjs.org/docs/advanced-features/static-html-export#caveats). So we'll have to change the build command to replace `export` with `start`. ([#1861](https://github.com/bloom-housing/bloom/pull/1861))
@@ -153,6 +175,8 @@ All notable changes to this project will be documented in this file. The format
   - StandardTable styling bug ([#1632](https://github.com/bloom-housing/bloom/pull/1632)) (Emily Jablonski)
   - More robust Features section for public listing view ([#1688](https://github.com/bloom-housing/bloom/pull/1688))
   - A11Y issues with the image tint in ImageCard ([#1964](https://github.com/bloom-housing/bloom/pull/1964)) (Emily Jablonski)
+  - Visual bugs with SiteHeader ([#2010](https://github.com/bloom-housing/bloom/pull/2010)) (Emily Jablonski)
+  - HouseholdSizeField bug when householdSizeMax is 0 ([#1991](https://github.com/bloom-housing/bloom/pull/1991)) (Yazeed)
 
 - Changed:
 
@@ -183,6 +207,7 @@ All notable changes to this project will be documented in this file. The format
     - **Breaking Change**: Moved tableHeader prop into new tableHeaderProps object
   - Re-wrote SiteHeader to remove Bulma dependency and bugs ([#1885](https://github.com/bloom-housing/bloom/pull/1885)) (Emily Jablonski)
     - **Breaking Change**: SiteHeader has a new prop set, including some props to toggle new visual features
+  - Set a max width for hero buttons when there are secondary buttons ([#2002](https://github.com/bloom-housing/bloom/pull/2002)) (Andrea Egan)
 
 ### Backend
 
@@ -206,6 +231,9 @@ All notable changes to this project will be documented in this file. The format
   - Added the optional jurisdiction setting notificationsSignUpURL, which now appears on the home page if set ([#1802](https://github.com/bloom-housing/bloom/pull/1802)) (Emily Jablonski)
   - Adds Listings managment validations required for publishing a Listing [#1850](https://github.com/bloom-housing/bloom/pull/1850) (Michał Plebański & Emily Jablonski)
   - Add UnitCreateDto model changes to prevent form submission from creating UnitType, UnitRentType and AccessibilityType from creating a new DB row on each submission. ([#1956](https://github.com/bloom-housing/bloom/pull/1956))
+  - Adds Program entity to Listing (Many to Many) and to Jurisdiction (Many to many) and seed programs ([1968](https://github.com/bloom-housing/bloom/pull/1968))
+  - Add Language to Jurisidiction entity ([#1998](https://github.com/bloom-housing/bloom/pull/1998))
+  - Add `DELETE /user/:id` and `GET /user/:id` endpoints and add leasingAgentInListings to UserUpdateDto
 
 - Changed:
 
@@ -227,6 +255,9 @@ All notable changes to this project will be documented in this file. The format
   - `amiPercentage` field on UnitsSummary is migrated to an integer instead of a string. ((#1797)[https://github.com/bloom-housing/bloom/pull/1797])
   - Change preferredUnit property to store unitType ids ([#1787](https://github.com/bloom-housing/bloom/pull/1787)) (Sean Albert)
   - Trying to confirm already confirmed user now throws account already confirmed error instead of tokenMissing ([#1971](https://github.com/bloom-housing/bloom/pull/1971))
+  - Updates CSV Builder service to work with any data set, predefined or not. ([#1955](https://github.com/bloom-housing/bloom/pull/1955))
+  - Remove field applicationAddress ([#2009](https://github.com/bloom-housing/bloom/pull/2009)) (Emily Jablonski)
+  - Introduce N-M Listing-Preference relation through a self managed (not TypeORM managed) intermediate entity ListingPreference, which now holds ordinal and page. Remove Preference entity entirely with an appropriate DB migration. ([1947](https://github.com/bloom-housing/bloom/pull/1947))
 
 - Fixed:
   - Added checks for property in listing.dto transforms

README.md

@@ -81,25 +81,27 @@ This runs 3 processes for both apps and the backend services on 3 different port
 - 3001 for the partners app
 - 3100 for backend/core
 
-### Versioning
+## Contributing
 
-We are using [lerna](https://lerna.js.org/) as a package versioning tool. It helps with keeping multiple package versions in sync for the entire monorepo. In conjunction with Lerna we are also using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), a specification for commit messages that helps tools like Lerna understand what level of change the commit is so that you can automate things like versioning, releases, and changelogs. On commit, three steps run: (1) linting, (2) a conventional commit CLI, and (3) a verification of the conventional commit standard. If you have trouble with the CLI you may need to install the tool globally with `npm install -g commitizen`.
+Contributions to the core Bloom applications and services are welcomed. To help us meet the project's goals around quality and maintainability, we ask that all contributors read, understand, and agree to our guidelines.
 
-## Releasing
+### Issue tracking
 
-PRs are opened to our dev branch. Netlify deploy previews are generated and automatically posted to all PRs. We have an application in Netlify for our dev environment that is published on every push to dev.
+Our development tasks are managed through GitHub issues and any development (in the vast majority of cases) should be tied to an issue. Even if you don't plan on implementing an issue yourself, please feel free to submit them if you run into issues. Before creating an issue, check first to see if one already exists. When creating an issue, give it a descriptive title and include screenshots if relevant. Please don't start work on an issue without checking in with the Bloom team first as it may already be in development! If you have questions, feel free to tag us on issues (@seanmalbert, @emilyjablonski) and note that we are also using GitHub discussions.
 
-Approximately weekly or as our roadmap requires us to, we will merge dev to master and then update our jurisdictional branches to get our changeset on a staging environment. Once that has been QA-ed we will publish to our production environment.
+### Committing, Versioning, and Releasing
 
-`ui-components` is currently released on an ad-hoc basis, but we will soon be implementing a more frequent automatic release.
+We are using [lerna](https://lerna.js.org/) as a monorepo management tool. It automatically versions, releases, and generates a changelog across our packages. In conjunction with lerna we are also using [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/), a specification for commit messages that helps lerna understand what level of change each commit is in order to automate our processes.
 
-## Contributing
+On commit, two steps automatically run: (1) linting and (2) a verification of the conventional commit standard. We recommend not running `git commit` and instead globally installing commitizen (`npm install -g commitizen`) and committing with `git cz` which will run a commit message CLI. The CLI asks a series of questions and builds the commit message for you in the conventional commit format. You can also `git commit` with a message if you are 100% confident you have indicated the right level of change (it will still lint the message format).
 
-Contributions to the core Bloom applications and services are welcomed. To help us meet the project's goals around quality and maintainability, we ask that all contributors read, understand, and agree to these guidelines.
+In addition to commits needing to be formatted as conventional commits, if you are making version changes across multiple packages, your commits must also be separated by package in order to not improperly version a package.
 
-### Issue tracking
+On every merge to dev, a pre-release of the ui-components package is automatically published to npm, and our Netlify dev environment is updated.
 
-Our development tasks are managed through GitHub issues and any development (in the vast majority of cases) should be tied to an issue. Even if you don't plan on implementing an issue yourself, please feel free to submit them if you run into issues. Before creating an issue, check first to see if one already exists. When creating an issue, give it a descriptive title and include screenshots if relevant. Please don't start work on an issue without checking in with the Bloom team first as it may already be in development! If you have questions, feel free to tag us on issues (@seanmalbert, @emilyjablonski) and note that we are also using GitHub discussions.
+On every merge to master (bi-weekly), a release of the backend/core and ui-components packages are automatically published to npm, and our Netlify staging environment is updated.
+
+Once staging has been QAed, we manually update production.
 
 ### Pull Requests
 

backend/core/.env.template

@@ -1,6 +1,6 @@
 PORT=3100
 NODE_ENV=development
-DATABASE_URL=postgres://localhost/bloom
+DATABASE_URL=postgres://localhost/bloom_detroit
 TEST_DATABASE_URL=postgres://localhost/bloom_test
 REDIS_TLS_URL=redis://127.0.0.1:6379/0
 REDIS_URL=redis://127.0.0.1:6379/0

backend/core/Aptfile

@@ -0,0 +1,2 @@
+# list packages
+lsof