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

API needs to be separated and expanded #20

Open
1 of 2 tasks
lizTheDeveloper opened this issue Jul 29, 2015 · 3 comments
Open
1 of 2 tasks

API needs to be separated and expanded #20

lizTheDeveloper opened this issue Jul 29, 2015 · 3 comments
Assignees

Comments

@lizTheDeveloper
Copy link
Contributor

We should have routes that handle views be distinct from routes that handle the API. I was listening for a "application/json" Accept header of the request, rather than an HTML or /, but having one route that handles all things is just stupid so let's do a simple change that will greatly simplify things because smartness.

  • Change all current view-serving routes to not serve json at all
  • Add an api REST route set(get post put delete) (in a diff file, name it api_modelNamePluralized.js) for each model
@lizTheDeveloper
Copy link
Contributor Author

Assigning this to you kick it back if ya don't wanna do it, then you could work on the iOS app and I could work on the front-end webapp.

@janardanyri
Copy link
Contributor

are you saying that if I do this I could work on the iOS app or to give this to you if I prefer to work on iOS? (I thought the consensus was that working on iOS doesn't make sense right now?)

@lizTheDeveloper
Copy link
Contributor Author

If you do this you could work on the iOS app, then I could do the backbone.js app.

@janardanyri janardanyri changed the title API is stupid API needs to be separated and expanded Jul 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants