Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

django Models #25

Closed
4 tasks done
zapplecat opened this issue Aug 15, 2016 · 6 comments
Closed
4 tasks done

django Models #25

zapplecat opened this issue Aug 15, 2016 · 6 comments
Assignees

Comments

@zapplecat
Copy link
Collaborator

zapplecat commented Aug 15, 2016

Models for various aspects of the game. Few are listed below, thought out with standard SQL columns. Add more in comments if necessary.

  • Auth (game) tokens: id, token, game_active
  • User tokens (paired with auth for active users): id, token
  • User: id, username, user token id, auth token id
  • Game rounds: id, round #, user id
@zapplecat zapplecat added this to the Back End Design milestone Aug 15, 2016
@zapplecat zapplecat self-assigned this Aug 15, 2016
@zapplecat
Copy link
Collaborator Author

zapplecat commented Aug 15, 2016

Added a few more items to game rounds: user_text, giphy_url, and game_over

@zapplecat
Copy link
Collaborator Author

Waiting on resolution on #26 before making pull request.

@corez92 corez92 mentioned this issue Aug 16, 2016
@zapplecat
Copy link
Collaborator Author

Will be redoing these to be more simple, one on one relationships.

@zapplecat
Copy link
Collaborator Author

zapplecat commented Aug 19, 2016

If people have no complaints on the current models structure, someone please merge and delete #30 branch.

@corez92
Copy link
Collaborator

corez92 commented Aug 19, 2016

Yeah, but how does this work? Do people have to fill in their username somewhere? I was thinking we could use sessions to identify unique people OR make like 4-6 basic usernames and people just use those to join a game, but that's the lame way lol

Anyway I think we need to sit down and discuss this model.

I also think there has to be a field called Initial_word that is True/False for the game round table. It checks to see if the entry is the initial one when the game starts.

@zapplecat
Copy link
Collaborator Author

I merged the initial model, but we can sit down to talk about this and make edits if necessary.

Re: your questions:

  1. Instead of the game immediately giving them their token, the user should type in a screen name. Then they will receive a game token. The reason the user token exists is for a REST API where the client can pass the user and game token and we (the server) will fact check their query.
  2. We don't need an initial_word field since we know which round is the first round, and we can just find the initial GameRounds.user_text off of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants