Allow user to specify an ad hoc name when submitting ad hoc attendance #485

Activity

1. pikachu0542

   added

   enhancement

   feature requestSomething you want, not something you needSomething you want, not something you need

   on Feb 23, 2026
2. NickJ-7010 commented on Sep 28, 2026

   

   NickJ-7010

   on Sep 28, 2026

   Contributor

   More actions

   I would like to take on this issue and could reasonably do it but I have some questions about the potential implementation.

   Currently the column for the directorships category is an enum with hardcoded potential values, to implement this, I think there are two ways you could go about it.

   1. You can remove the enum restriction and then have everything entered as a raw string with Ad-Hocs being able to be dynamic to the current active Ad-Hocs. This changes the database scheme but doesn't require any new / changed code for displaying the Ad-Hoc's name. You also would only need new code for the frontend form and for the single backend endpoint that needs to format the Ad-Hoc name.
   2. You could add an extra column to the table which specifies the Ad-Hoc's name and only gets used when an Ad-Hoc row is being added. This would keep the current enum enforcement but would require that the Ad-Hoc's name be read and formatted in every place that the directorship's name is currently being displayed (and future).

   I would personally recommend option 1 because it would be the cleanest drop-in implementation but I can understand the desire to keep the column enforced by the enum.

   For the Ad-Hoc formatting I am proposing one of the following:

   • Ad-Hoc "{name}"
   • Ad-Hoc ({name})
   • {name} (Ad-Hoc)
   • "{name}" (Ad-Hoc)
   • "{name}" Ad-Hoc
3. BigSpaceships commented on Oct 1, 2026

   

   BigSpaceships

   on Oct 1, 2026

   Contributor

   More actions

   added in #623
4. BigSpaceships

   closed this as completedon Oct 1, 2026