Request body for addPerson endpoint
{
personInfo: {
firstName: string (not null)
lastName: string (not null)
middleName: string
suffix: string
nickName: string
techAlumniChapter: string --> maybe give a list of chapters in the front end to choose from?
classYear: int (not null)
gradYear: int
gradSemester: int
gender: string (accepted values: male. female, other) --> make this a choice in the front end, not something to enter in a text box
}
degrees: [
{
subject: string (not null),
degreeType: string (accepted values: "AS", "BS", "MS", "PhD") --> make a dropdown menu to choose from in front end for this
degreeYear: int (not null),
degreeDescription: string (max 255 chars)
},
{
subject,
degreeType,
degreeYear,
degreeDescription
},
....
],
addresses: [
{
address1: string (not null),
address2: string, -- not sure if we need this
city: string (not null),
state: string (not null),
country: string (not null),
zipCode: int,
preferredAddress: boolean
},
{
** ADD ANOTHER ADDRESS HERE IF NECESSARY
}
],
contacts: [
{
contactNumber: string --> i guess this can be a phone nunber, email, etc.
contactType: string --> need to define list: phone, email, ....
preferredContact: boolean
},
..... more contacts if needed
],
involvements: [
involvement1: string,
involvement2: string ,
.... more if needed
]
}
Notes:
- for the front end, try to make user error as hard as possible
example: for gender provide a way to choose from male, female, other rather than have the user type in the gender
- this makes it so that a person can have 0 or many degrees, contacts, involvements, or addresses. If a person does not
have any of these, make the list be empty.
- if any value is not given (example: graduation date for a person who did not graduate), leave that value as null in the
request to the backend server
Name | Last commit | Last update |
---|---|---|
.. | ||
public | ||
src | ||
.env.development | ||
.env.production | ||
.gitignore | ||
Dockerfile | ||
README.md | ||
package-lock.json | ||
package.json |