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

Reroute /sprite into /api/v1/sprite #27

Closed
ljvmiranda921 opened this issue Apr 18, 2020 · 0 comments · Fixed by #32
Closed

Reroute /sprite into /api/v1/sprite #27

ljvmiranda921 opened this issue Apr 18, 2020 · 0 comments · Fixed by #32
Labels
backend Backend-related issues for the Python stack

Comments

@ljvmiranda921
Copy link
Owner

Related to #6

@ljvmiranda921 ljvmiranda921 added the backend Backend-related issues for the Python stack label Apr 18, 2020
@ljvmiranda921 ljvmiranda921 added this to To do in Phase 1: Proof-of-Concept via automation Apr 18, 2020
ljvmiranda921 added a commit that referenced this issue Apr 19, 2020
Resolves #27
Reference #6

It's good to standardize the route under /api, then we just add versions
as we go. I won't be closing #6 because the main goal there is to create
a better "templating" system for the backend.

Signed-off-by: Lester James V. Miranda <ljvmiranda@gmail.com>
Phase 1: Proof-of-Concept automation moved this from To do to Done Apr 19, 2020
ljvmiranda921 added a commit that referenced this issue Apr 19, 2020
Resolves #27
Reference #6

It's good to standardize the route under /api, then we just add versions
as we go. I won't be closing #6 because the main goal there is to create
a better "templating" system for the backend.

Signed-off-by: Lester James V. Miranda <ljvmiranda@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend-related issues for the Python stack
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant