Skip to content

Update Table: User | Model | API | Test cases#616

Open
Ruchitha12 wants to merge 1 commit intohackforla:mainfrom
Ruchitha12:feature/update_user
Open

Update Table: User | Model | API | Test cases#616
Ruchitha12 wants to merge 1 commit intohackforla:mainfrom
Ruchitha12:feature/update_user

Conversation

@Ruchitha12
Copy link
Copy Markdown
Member

Fixes #601

What changes did you make?

  • Updated and added a few fields to the User model
  • Updated the User API serializer
  • Generated and documented the updated core_user table schema.

Why did you make the changes (we will use this info to test)?

  • To align the User model with the updated intake schema requirements.

Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)

  • No UI, only backend changes

@fyliu fyliu force-pushed the feature/update_user branch from cc66bb1 to c93f0e2 Compare February 12, 2026 23:32
@fyliu
Copy link
Copy Markdown
Member

fyliu commented Feb 12, 2026

I rebased to main and updated the migration file numbering, making sure tests and linters are passing. I haven't looked at the code yet.

@fyliu fyliu moved this to 👀PR being reviewed in P: PD: Project Board Feb 12, 2026
Copy link
Copy Markdown
Member

@fyliu fyliu left a comment

Choose a reason for hiding this comment

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

Thanks for working on this! I think we need some clarification on the requirements for this to be sure. I will bring it up at the meeting.

Comment on lines +114 to +119
intake_target_skills = ArrayField(
base_field=models.IntegerField(),
default=list,
blank=True,
)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think this might need to be a many to many reference to another table. Let me ask to make sure.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Linking to the clarification from the meeting. This does look like the structure that's intended. Let me make sure there's nothing significantly better for this.

@github-project-automation github-project-automation bot moved this from 👀PR being reviewed to PR changes requested in P: PD: Project Board 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

Status: PR changes requested

Development

Successfully merging this pull request may close these issues.

Update Table: User

2 participants