#49 Extract Submitter Information

BasicallyOk commented 5 months ago

What does this PR do?

Allow the submission to be categorized as needed (submitter demographic, substance used, ....)

Github Issue Number

Resolves: #49 #40

Relates to: #32 (modifying some stuff to match specs), #27 (handles some of the logic of the submission button in front end because I need it for testing)

Author checklist

If any of these points have yet to be satisfied, make sure that you set the title to the format DRAFT #issue-num Title

[x] The title is short and descriptive of the PR. Must start with the Github Issue Number (format: #issue-num Title).
[x] The description follows proper cl description practices and mentions related Github Issues (make sure this is the first thing you mention).
[x] Branch has merged in the latest version of main
[x] Linting has occured, as per the project linting config
[x] All changed functions have proper docstring/wiki updates (front-end team) to describe what they do and how to use them.
[x] Add yourself as the assignee.
[x] Add reviewer a reviewer and let them know on discord.
[x] Ensure that all relevant ticket has been linked to the PR

Reviewer checklist

[x] Relevant issue is mentioned in description
[x] Code solves the issue
[x] Code follows the specification
[x] Code is the best solution for the issue
[x] Branch is ahead of main
[x] Ensures the fix/feature works locally

mustafa-tariqk commented 5 months ago

conflict + catch up to main and i'll merge

BasicallyOk commented 5 months ago

Remind me to add the specs to Wiki

mustafa-tariqk / mindscape