search

clevr / quest-board

A gamified to-do application (╯°□°）╯︵ ┻━┻
0 stars 0 forks source link

list of api endpoints? #2

Open airondumael opened 9 years ago

airondumael commented 9 years ago

will it help if will plan all the api endpoints that we will be needing before starting with the backend?

I think this will help with the consistency of our endpoints.

wildtron commented 9 years ago

best way to do a collated list of endpoints?

airondumael commented 9 years ago

How about we create first the list of endpoints we think will be needing and create documentation (apidocs?) of what we want it to look like and code from there?

@clevr/prime , any suggestions?

cedricabuso commented 9 years ago

I agree with @airondumael. :)

wildtron commented 9 years ago

oke, so what's the best util we use to list api endpoints we need?

eshleebien commented 9 years ago

apidocs

wildtron commented 9 years ago

i mean, we "list" first before we doc

wildtron commented 9 years ago

ie. sheets..

eshleebien commented 9 years ago

yes ie. Internet explorer :))

jekku commented 9 years ago

:+1:

airondumael commented 9 years ago

github wiki?

wildtron commented 9 years ago

oke, we use github wiki

cedricabuso commented 9 years ago

Github wiki :+1:

wildtron commented 9 years ago

see Endpoints if this should suffice.

airondumael commented 9 years ago

why not dungeon instead of d?

wildtron commented 9 years ago

we make it short and simple and single letters look cool. if we have endpoints with same prefix, we add the next letter of that endpoint eg. dungeon - d, deck - de, something like that

cedricabuso commented 9 years ago

I think it would be better if we use the whole word for the endpoints to become more readable and to be easily understood on what that endpoint will do.

airondumael commented 9 years ago

I agree with ced, if the api grows it will be harder to understand what that endpoint does.

cedricabuso commented 9 years ago

LOL, *word

eshleebien commented 9 years ago

i agree with ced too