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

fix: comment out income validation and change to text field #620

Merged
merged 3 commits into from
Jun 5, 2023

Conversation

emilyjablonski
Copy link
Collaborator

@emilyjablonski emilyjablonski commented Jun 5, 2023

Pull Request Template

Issue Overview

Support issue Slack thread

  • This change addresses the issue in full
  • This change addresses only certain aspects of the issue
  • This change is a dependency for another issue
  • This change has a dependency from another issue

Description

This is a temporary fix that we hope will allow folks to continue past the income step. It removes all validation on the field, but does still require it.

How Can This Be Tested/Reviewed?

Try to submit an application with non-numeric characters + numbers that are well above and below the listing's limits.

In partners it should display as that string.

Checklist:

  • My code follows the style guidelines of this project
  • I have added QA notes to the issue with applicable URLs
  • I have performed a self-review of my own code
  • I have reviewed the changes in a desktop view
  • I have reviewed the changes in a mobile view
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have assigned reviewers
  • I have run yarn generate:client and/or created a migration if I made backend changes that require them
  • My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
  • Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

  • Read and understand the issue, and ensure the author has added QA notes
  • Review the code itself from a style point of view
  • Pull the changes down locally and test that the acceptance criteria is met
  • Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
  • Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

@netlify
Copy link

netlify bot commented Jun 5, 2023

Deploy Preview for housing-sanjoseca-gov ready!

Name Link
🔨 Latest commit c55ee9b
🔍 Latest deploy log https://app.netlify.com/sites/housing-sanjoseca-gov/deploys/647e6b7a5ba2a4000834fdbf
😎 Deploy Preview https://deploy-preview-620--housing-sanjoseca-gov.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@netlify
Copy link

netlify bot commented Jun 5, 2023

Deploy Preview for hba-public-main ready!

Name Link
🔨 Latest commit c55ee9b
🔍 Latest deploy log https://app.netlify.com/sites/hba-public-main/deploys/647e6b7a781c020007bc1d99
😎 Deploy Preview https://deploy-preview-620--hba-public-main.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Copy link
Collaborator

@ludtkemorgan ludtkemorgan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Emily!

Copy link
Collaborator

@YazeedLoonat YazeedLoonat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@emilyjablonski emilyjablonski merged commit f56fdad into main Jun 5, 2023
ludtkemorgan added a commit that referenced this pull request Jun 13, 2023
ludtkemorgan added a commit that referenced this pull request Jun 14, 2023
* 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>
@ludtkemorgan ludtkemorgan mentioned this pull request Oct 12, 2023
19 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants