Skip to content

Regenerate application migration with pandadoc-matching fields#117

Closed
SamNie2027 wants to merge 254 commits intomainfrom
171-regenerate-application-migration
Closed

Regenerate application migration with pandadoc-matching fields#117
SamNie2027 wants to merge 254 commits intomainfrom
171-regenerate-application-migration

Conversation

@SamNie2027
Copy link

ℹ️ Issue

Closes

📝 Description

Regenerates application migration with the bare minimum new enums needed for it to work. Also removed the old migration tables

✔️ Verification

\dt and \d application show the correct output

bhchp=# \d application
                                                      Table "public.application"
            Column            |              Type               | Collation | Nullable |                   Default   

------------------------------+---------------------------------+-----------+----------+----------------------------------------------
 appId                        | integer                         |           | not null | nextval('"application_appId_seq"'::regclass)
 email                        | character varying               |           | not null | 
 discipline                   | application_discipline_enum     |           | not null |
 otherDisciplineDescription   | character varying               |           |          |
 appStatus                    | application_appstatus_enum      |           | not null | 'App submitted'::application_appstatus_enum
 mondayAvailability           | character varying               |           | not null | 
 tuesdayAvailability          | character varying               |           | not null |
 wednesdayAvailability        | character varying               |           | not null |
 thursdayAvailability         | character varying               |           | not null | 
 fridayAvailability           | character varying               |           | not null |
 saturdayAvailability         | character varying               |           | not null |
 experienceType               | application_experiencetype_enum |           | not null | 
 interest                     | application_interest_enum       |           | not null |
 license                      | character varying               |           | not null |
 phone                        | character varying               |           | not null | 
 applicantType                | application_applicanttype_enum  |           | not null |
 school                       | application_school_enum         |           | not null | 
 otherSchool                  | character varying               |           |          |
 referred                     | boolean                         |           |          | false
 referredEmail                | character varying               |           |          |
 weeklyHours                  | integer                         |           | not null |
 pronouns                     | character varying               |           | not null |
 nonEnglishLangs              | character varying               |           |          | 
 desiredExperience            | character varying               |           | not null |
 coverLetter                  | character varying               |           | not null |
 emergencyContactName         | character varying               |           | not null |
 emergencyContactPhone        | character varying               |           | not null |
 emergencyContactRelationship | character varying               |           | not null |
Indexes:
    "PK_application_appId" PRIMARY KEY, btree ("appId")
Referenced by:
    TABLE "learner_info" CONSTRAINT "FK_learner_info_appId" FOREIGN KEY ("appId") REFERENCES application("appId") ON DELETE CASCADE
    TABLE "volunteer_info" CONSTRAINT "FK_volunteer_info_appId" FOREIGN KEY ("appId") REFERENCES application("appId") ON DELETE CASCADE

🏕️ (Optional) Future Work / Notes

The old enums are still at the old values: that will be worked on in a future ticket.
The seeding for applications is still commented out because the enums are operating with new values - which the types are to also be updated in that same future ticket, but for now they are still commented out.

piersolh and others added 30 commits September 16, 2025 22:07
[Issue #16] -  create discipline entity in TypeORM
added testing
removed deprecated on update
adding user authentication by adding provider
deleted old migration file and used just the main one
chnnick and others added 28 commits February 7, 2026 19:54
migrations for creating learner and volunteer info tables
…plications-by-discipline

implemented endpoints
…ine dto, added tests and comments for new dto
Removed updateApplicationInterest dto, added updateApplicationDiscipl…
…lication

Adds all pandadoc fields that were missing
@SamNie2027 SamNie2027 changed the title 171 regenerate application migration Regenerate application migration with pandadoc-matching fields Feb 12, 2026
@SamNie2027 SamNie2027 closed this Feb 12, 2026
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.