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

Decide on and create specification for the API endpoints in the White Paper #253

Closed
Monstarrrr opened this issue Jul 4, 2024 · 2 comments
Assignees
Labels
[ backend / decision For tracking decisions [ documentation / Improvements or additions to documentation [ frontend /

Comments

@Monstarrrr
Copy link
Owner

Monstarrrr commented Jul 4, 2024

Problem

There is no specification in the white paper about what the API endpoints should be, which makes it more tedious to come up with coherent endpoints (for both front-end and back-end) during development

Solution

Let's create a specification for the API endpoints in the White Paper
https://docs.google.com/document/d/1YD5JONwXirWWoSGQblhfEtk968Ux9Y2Sgw0Dd9XnpuI

@Monstarrrr Monstarrrr added [ documentation / Improvements or additions to documentation [ frontend / [ backend / decision For tracking decisions labels Jul 4, 2024
@Monstarrrr Monstarrrr changed the title Decide on and create specification for the API endpoints Decide on and create specification for the API endpoints in the White Paper Jul 5, 2024
@purple-void
Copy link
Collaborator

kind of a repeat of #248

@Monstarrrr
Copy link
Owner Author

kind of a repeat of #248

Yeah, I think we'll go for creating the full list straight away inspired by stackoverflow's API, and then clarify any MVP exceptions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[ backend / decision For tracking decisions [ documentation / Improvements or additions to documentation [ frontend /
Projects
Status: Done
Development

No branches or pull requests

3 participants