TODOs

in the MUNify Repository

Total: – 59

• ./package.json:12

  "

• ./chase/rust-backend/src/error.rs:32

  check which errors are safe to return to the frontend and do so for debugging

• ./chase/backend/README.md:2

• ./chase/backend/tsconfig.json:7

  currently deactivated due to errors when building the frontend

• ./chase/backend/src/main.ts:10

  switch to new prismabox schema types

• ./chase/backend/src/main.ts:11

  remove use of set where applicable

• ./chase/backend/src/routes/user.ts:10

• ./chase/backend/src/routes/agendaItem.ts:38

  is this used? @TadeSF

• ./chase/backend/src/routes/auth/auth.ts:205

  : report back errors in sending emails to the frontend in structured way

• ./chase/backend/src/routes/auth/auth.ts:224

  spam protection?

• ./chase/backend/src/routes/auth/auth.ts:252

  : report back errors in sending emails to the frontend in structured way

• ./chase/backend/src/auth/session.ts:7

  periodically purge old sessions? Or does redis do that for us?

• ./chase/backend/src/auth/abilities/abilities.ts:79

• ./chase/backend/src/auth/abilities/entities/speakersList.ts:32

  : Restrict field access for non admins further

• ./chase/backend/src/util/config.ts:1

  : We should probably use a library for this

• ./chase/backend/prisma/schema.prisma:37

  a max amount for passwords would make sense

• ./chase/backend/prisma/schema.prisma:246

  replace this with a signle linked list for better concurrency/less necessary updates?

• ./chase/backend/prisma/schema.prisma:270

  should we allow for customizing these per conference and just allow loading template at creation?

• ./chase/backend/prisma/seed.ts:200

  Kosovo, only temporary for MUNBW 2024

• ./chase/frontend/README.md:2

• ./chase/frontend/app/(pages)/login/validateEmail/page.tsx:55

  : these error messages are copied into the html and therefore are not responsive to language changes

• ./chase/frontend/app/app/[conferenceId]/admin/teampool/page.tsx:24

• ./chase/frontend/app/app/[conferenceId]/admin/structure/page.tsx:31

• ./chase/frontend/app/app/[conferenceId]/admin/committees/page.tsx:22

• ./chase/frontend/app/app/[conferenceId]/admin/configs/page.tsx:19

• ./chase/frontend/app/app/[conferenceId]/admin/configs/page.tsx:26

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/regional_groups/page.tsx:28

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/participant/layout.tsx:60

  add Voting Page

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/participant/layout.tsx:65

  add Resolution Editor page

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/participant/dashboard/page.tsx:24

  Check why this Scroll Bar is not changing color as the other ones with the custom-scrollbar class

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/participant/speakers/page.tsx:14

  this is unused

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/layout.tsx:56

  add Voting page

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/layout.tsx:72

  add Resolution Editor page

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/dashboard/page.tsx:38

  Check why this Scroll Bar is not changing color as the other ones with the custom-scrollbar class

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/voting/page.tsx:23

  : Add dialog for creating a new motion

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/voting/page.tsx:24

  : Add dialog for creating a new voting out of a motion

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/voting/page.tsx:25

  : Add dialog for changing the information of a voting

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/inbox/page.tsx:20

• ./chase/frontend/app/app/[conferenceId]/committee/[committeeId]/chair/inbox/page.tsx:23

• ./chase/frontend/app/app/[conferenceId]/hub/team/inbox/page.tsx:8

  we should use a context for message storage

• ./chase/frontend/hooks/useBackendCall.ts:18

  we could do some actual error handling instead of just throwing

• ./chase/frontend/misc/get_flag_path_by_code.tsx:10

  - this is a temporary solution until we have the correct logos

• ./chase/frontend/contexts/user_ident.tsx:79

  nullable types cleanup throughout the whole app

• ./chase/frontend/components/cookie_banner.tsx:32

  : Fix cookie interference with the backend

• ./chase/frontend/components/lockout.tsx:23

  fix this type error

• ./chase/frontend/components/dashboard/documents.tsx:30

  Find a better solution for height limiting

• ./chase/frontend/components/dashboard/whiteboard.tsx:24

  find a better solution for scaling the Whitboard Box

• ./chase/frontend/components/dashboard/actions_overlay.tsx:137

  File Upload

• ./chase/frontend/components/dashboard/actions_overlay.tsx:212

  type "props" correctly

• ./chase/frontend/components/dashboard/chair/agenda_selection.tsx:22

• ./chase/frontend/components/dashboard/chair/agenda_selection.tsx:64

  Implement Chairs creating new Agenda Items

• ./chase/frontend/components/dashboard/chair/regional_groups_lookup.tsx:32

• ./chase/frontend/components/dashboard/chair/set_status.tsx:55

• ./chase/frontend/components/navbar/external_links.tsx:17

• ./chase/frontend/components/navbar/settings_sidebar.tsx:133

  Settings

• ./chase/frontend/components/speakers_list/change_speech_time.tsx:26

  : Add a default value

• ./chase/frontend/components/speakers_list/country_auto_complete.tsx:61

  this does not work as expected and I (Tade) am not sure what this even is supposed to do

• ./chase/frontend/components/speakers_list/add_speaker.tsx:26

  add warning when a speaker is added to the list and the list is closed

• ./chase/frontend/components/attendance/presence_widget.tsx:163

  this is probably only a good temporary solution.