sgronlund / latias-backend Goto Github PK

Seems like we have duplicate worksflows and that the test workflow has disappeared.
Seems to be a mistake on a recent change.

Dont have the .yml file at hand so cannot do it myself.

Our main function should be one file and all the functions in another file.

On the front-end, we'll want to display all questions related to the current week in different screens (or the same screen, just re-rendered). This means we'll have to ask the server to return a specific question for each page (since we don't want duplicate questions). But now we have no way to actually separate questions and we can't assume the front-end should keep track of what each question is. There are three approaches to this issue that I can think of.

1. We redo our askQuestion function to return all questions related to the week instead of just one. After that we can let the client side keep track of which questions it has already used itself. The downside to this is that it's quite tricky to keep track of arguments between screens and we may also want to exclude as much logic as possible on the front-end.

2. We include another argument in the askQuestion function that would be a number. The advantage of this is that we won't have to store anything on the client-side since we could simply say on the page for the first question that we want to fetch question number one and on the second page we could fetch question number two and so on. This means we only have to keep track of which page we are on. The downside however is that we have to make more emits between server and client.

3. After we've fetched a question, we remove that question from the database automatically, which means we won't ever get duplicate questions. This would eliminate even more logic from the front-end since we wouldn't even need to include a number (server could just randomize a question to fetch).

At the moment, the same user can log in twice from two different devices. We could implement this by checking if the user is already in the users array.

Linked with sgronlund/latias-proj#49

Just adding this issue so that I remember, I'll do it later tonight.

Should also store the users balance in the database permanently

If we merge #24, the getQuestion function is no longer used since we use the getQuestions function instead to return all questions at once.

Now the server just counts down from a week. Ideally, we would want to open the quiz every Saturday or so.

This actually turns out to be more difficult than what I first thought. The problem is the salting and hashing is affected by if the user enters something upper/lower-case and therefore we need to transform everything to upper-case before doing any hashing or salting. This includes the client side.

4 at the moment

0 < Week number <= 52

We need to return different values for success, invalid email input, trying to login as root and invalid input