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

Update dropdown values intake forms, DB migration to convert previous values to new values #231

Merged
merged 4 commits into from
Jan 9, 2025

Conversation

wilwong89
Copy link
Contributor

Description

Migrate several data values from old data to new data.
See tickets for details: PADS 403, PADS 412
Modify CHEFS imports to account for value changes
Update dropdown values in intakes forms to account for new values.
Update tests related to intake forms.

Types of changes

New feature (non-breaking change which adds functionality)

Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the CONTRIBUTING doc
  • I have checked that unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

Copy link

github-actions bot commented Dec 24, 2024

Coverage Report (Frontend)

Totals Coverage
Statements: 46.39% ( 3204 / 6907 )
Methods: 35.43% ( 411 / 1160 )
Lines: 54.31% ( 1871 / 3445 )
Branches: 40.05% ( 922 / 2302 )

Copy link

github-actions bot commented Dec 24, 2024

Coverage Report (Application)

Totals Coverage
Statements: 37.17% ( 1066 / 2868 )
Methods: 26.43% ( 129 / 488 )
Lines: 48.51% ( 701 / 1445 )
Branches: 25.24% ( 236 / 935 )

@qhanson55
Copy link
Collaborator

I'm worried about using isDevelopedByCompanyOrOrg for Business or Individual it's not very intuitive. It may be my misunderstanding but to me isDevelopedByBusinessOrIndividual or something along those lines is more applicable. I think this is an old chefs value or something? If we're going to be keeping this DB as is we should try and move forward with using names that make sense to their use cases. Especially if we're doing a migration in this PR anyways.

app/src/docs/v1.api-spec.yaml Show resolved Hide resolved
app/src/docs/v1.api-spec.yaml Outdated Show resolved Hide resolved
app/src/docs/v1.api-spec.yaml Outdated Show resolved Hide resolved
app/src/utils/enums/housing.ts Show resolved Hide resolved
app/src/controllers/submission.ts Outdated Show resolved Hide resolved
app/src/docs/v1.api-spec.yaml Show resolved Hide resolved
frontend/src/utils/enums/housing.ts Show resolved Hide resolved
app/src/utils/enums/housing.ts Show resolved Hide resolved
@wilwong89 wilwong89 force-pushed the feature/data-conversion branch from 503942a to 4a6a314 Compare January 2, 2025 23:34
@wilwong89 wilwong89 closed this Jan 2, 2025
@wilwong89 wilwong89 reopened this Jan 2, 2025
Created new migration
Edited constants for front and backend
Modified FE/BE validators
Updated tests
@wilwong89 wilwong89 force-pushed the feature/data-conversion branch 2 times, most recently from 1ef2056 to c2e65b0 Compare January 8, 2025 19:27
@wilwong89 wilwong89 force-pushed the feature/data-conversion branch from c2e65b0 to a9e39d0 Compare January 8, 2025 19:45
@qhanson55 qhanson55 merged commit c5aa6fd into master Jan 9, 2025
18 of 19 checks passed
@qhanson55 qhanson55 deleted the feature/data-conversion branch January 9, 2025 19:27
@kyle1morel kyle1morel mentioned this pull request Jan 10, 2025
4 tasks
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.

4 participants