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.

Sign up for GitHub

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

Jump to bottom

GraphQL Support #42

Open
pacharanero opened this issue Jun 24, 2020 · 0 comments
Open

GraphQL Support #42

pacharanero opened this issue Jun 24, 2020 · 0 comments
Labels
design-decision An issue that documents a past, present or future design decision in the project nice-to-have A feature which would be nice to have but is not essential not-for-mvp Not required for MVP launch

Comments

@pacharanero
Copy link
Member

At this stage, and with such a simple API structure, we probably don't need to worry about GraphQL, however in the future it may be something to consider adding if it is necessary
@pacharanero pacharanero added design-decision An issue that documents a past, present or future design decision in the project nice-to-have A feature which would be nice to have but is not essential not-for-mvp Not required for MVP launch labels Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design-decision An issue that documents a past, present or future design decision in the project nice-to-have A feature which would be nice to have but is not essential not-for-mvp Not required for MVP launch
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pacharanero