-
Notifications
You must be signed in to change notification settings - Fork 12
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
Back-end planning. #7
Comments
Assigned #5 to @Dex-theDev |
added #14 thanks to @JoeDravarol so we can decide on which free hosting provider to choose. |
I would like to tackle the implementation of the API, I would love to delve more into the backend this way and I am currently looking into the APIs available for the memory game. Naturally, I will come to the group for any issues I cannot solve or do not understand after all this is a learning experience. The API would return certain data based on what we are developing the memory game over, whether it is the pokemon card's in general or pokemon types, and that data would be returned into JSON format. This is open to discussion. |
If you'd like to tackle the api you can. The api needs to return Pokemon cards. I think an array that randomizes the order of the cards is best. I'm thinking 8 different cards, and each one will need to be in the array twice in a different order. It should also return a singular picture that will act as the back of the card. Does this sound like what were you thinking? |
Sounds about right, I'll first do some testing with what is returned from the API, update you all on the process as I work on it. |
Added #18, this is a issue to further help with readability, doesn't need a proposal since its a small change in code and I have outline the changes i would like have done.
thanks for the proposal, and it sounds like you got the ok from @jericashall. The further clarification from her did help me understand. If you can further break down theses tasks in #4 that would be helpful. If not then not a big deal. |
Ive talked to the front end group on vc chat and also wrote a message here, once the front end devs decide on what they data they want from you the backend group, make sure you decide if you need any data from the client. This group needs to define what input you need from the front-end to achieve the desired outcome that front-end devs want. of course you can also bring up issues that you know we will need, like having a shuffling function (it was mentioned that we can use the fisher-yates shuffle to randomly shuffle the array), also setting up the api for fetching random pokemon to send the image urls as part of the array will be necessary. going from what i wrote in the message i assume you need you need a couple of parameters name="name of the player"
// AFAIK parameters sent from the client should be done with an underscore
// should be false or true, it denotes whether we keep track of time as well.
pause_state = true
// make sure to check if this is empty, as that means the game just started,
// otherwise it will have a array value which is picked by the user
choice="" this is a mockup of #15 and its a rough idea of what if i was in your situation i would ask from the front-end. Of course i would wait from the front-end devs to finalize a specification. |
Currently, I have decided with the Pokemon TCG API, it is a private API, I spent the day looking for better APIs, however for the desired data it is the best choice, it is a private API so I will be setting up an account and acquiring a key and will send it in the discord chat, there are a few questions with implementing it using the key within the header that I am not familiar with, so I will contact you tomorrow regarding that @MichaelPachec0 |
I'd like to take a shot at #18 since it doesn't need a proposal I'm going to assign myself |
Happy to help with any backend issue you guys assign to me! |
Before that Is there a way I can reach you on discord? My discord is m1chael#3550 feel free to add me as a friend so i can discuss some specifics of this repository/project. |
Just sent a friend request! |
This will be used as conversation on how the back-end will be structured and will reference other issues pertaining to more specific bugs/enhancements. The specific issues that will be referenced here can then be assigned individually.
Issues to tackle:
The text was updated successfully, but these errors were encountered: