Basic Database Structure

Utkub24 commented 7 months ago

[ ] I have not added anything unrelated of this PR to the PR message (I had to make the joke sry)

Closes #1

I (@HuseyinSimsek7904 not @Utkub24) got bored so I decided to create database services for the project. I did not have 5 PRs that are ready and waiting for review, so you are completely right to say that I should not be bored.

Explanation of the contents of the PR

The PR has two main parts: the makefile and interface/service/controllers for the database. The makefile is updated so that the developer can generate a valid database for experiments and tests. The code changes contain new interfaces and other database management programs for the database entries types: user, raffle and participant. There is also formQuestion interface which is used for storing the information of the form questions that the raffle table contains.

Future plans

Currently we do not have any plans. We should discuss this as soon as possible.

Notes

This PR contains breaking changes about the .env file. Please update your it after this PR according to the wiki entry.
All of the raffles that the makefile generates have an empty form field.
I can not add @Utkub24 as a reviewer as he is the owner of the PR, but I want him to review as well.

HuseyinSimsek7904 commented 7 months ago

Please before continuing your work @Utkub24, refresh your .env file according to the wiki entry. I had to update its variable names so that both the Makefile and the nestJS application could use it without weird name conventions and redefinitions.

HuseyinSimsek7904 commented 7 months ago

@Utkub24 Why would you remove the checklist before converting the PR from a draft? Now we have to manually copy-paste them after we are done.

Let's not remove these checklists before the PR is ready.

Utkub24 commented 7 months ago

copy-paste

Is this intentional?

HuseyinSimsek7904 commented 7 months ago

copy-paste

Is this intentional?

'course it is.

HuseyinSimsek7904 commented 7 months ago

@Utkub24 I need your help writing the description here. I think the PR is ready.

erthium commented 7 months ago

I checked the files a bit, as for follow-up suggestions, we need to have to routes to be used in the client side that:

Checks if a raffle ID is valid or not, if so, checks the senders IP address and determines if they have submitted before, if so, we will send a special respons telling us in the front-end to show the user 'Thanks for submitting!' component.
Gets the raffle data/information which needs to be stripped from confidential data, like we may want to exclude author info, any participant relation etc. if there is any

erthium commented 7 months ago

Will also check the PR very soon, things seem pretty cool though, good job :+1:

erthium commented 7 months ago

Also for follow-up, we do not have routes for registering participants, and creating new raffles

HuseyinSimsek7904 commented 7 months ago

Also for follow-up, we do not have routes for registering participants, and creating new raffles

Oh, right. Can you please create an issue for this? Or separate issues?

Duck-Tech-Dev / api-winnerduck