The PR itself removes the questionOptionType column which can be either Title, Subtitle, or Null from registration fields,including the functionality to pass this data to the question options table. Furthermore, this PR removes the questionId column in registrationFields.
Furthermore, I kept the registrationId and userId in the `questionOptions table to be able to uniquely identify a question option by user and registration. Furthermore, setting registrationId and userId equal to null retains the functionality to set custom question options that are defined by us.
Seed changes
create separate functions that generate the seed data for each entity (e.g., generateEventData, generateUserData, generateGroupData). These functions should accept the necessary parameters or configurations to generate the desired seed data.
moved the logic for generating seed data from the seed function into these separate functions.
the seed function itself will inserts the provided seed data into the database using the existing helper functions (createEvent, createCycle, etc.).
Note
This PR should only be merged to develop once the admin feature to handle the the transition from registrations to question options gets developed (please review the admin feature: https://github.com/lexicongovernance/pluraltools-admin/pull/99)
Database and Service changes
The PR itself removes the
questionOptionTypecolumn which can be eitherTitle,Subtitle, orNullfrom registration fields,including the functionality to pass this data to the question options table. Furthermore, this PR removes thequestionIdcolumn in registrationFields.Furthermore, I kept the
registrationIdanduserIdin the`questionOptionstable to be able to uniquely identify a question option by user and registration. Furthermore, setting registrationId and userId equal tonullretains the functionality to set custom question options that are defined by us.Seed changes