Split Role and Person info in frontend
To make handling info about roles and persons easier we split them into separate objects. The Profile page has now gotten its own api endpoint where a sponsor has access to all guests instead of only those they are sponsor for which is used on the sponsor frontpage. This is necessary since a sponsor may want to give a role to someone they are not currently sponsor for.
Showing
- frontend/src/interfaces/index.ts 24 additions, 15 deletionsfrontend/src/interfaces/index.ts
- frontend/src/routes/sponsor/frontpage/index.tsx 35 additions, 14 deletionsfrontend/src/routes/sponsor/frontpage/index.tsx
- frontend/src/routes/sponsor/guestInfo/index.tsx 55 additions, 21 deletionsfrontend/src/routes/sponsor/guestInfo/index.tsx
- frontend/src/routes/sponsor/guestRoleInfo/index.tsx 14 additions, 9 deletionsfrontend/src/routes/sponsor/guestRoleInfo/index.tsx
- frontend/src/routes/sponsor/index.tsx 15 additions, 20 deletionsfrontend/src/routes/sponsor/index.tsx
- frontend/src/utils/index.ts 15 additions, 0 deletionsfrontend/src/utils/index.ts
- gregui/api/urls.py 2 additions, 0 deletionsgregui/api/urls.py
- gregui/api/views/person.py 46 additions, 0 deletionsgregui/api/views/person.py
- gregui/views.py 28 additions, 21 deletionsgregui/views.py
Loading
Please register or sign in to comment