TODO file

[lukaszx0]

Let's keep todo list in repo

/cc @spastorino

[coveralls]

Coverage remained the same when pulling 6045601 on strzalek:create-todo into 3abbbc6 on rails-api:rewrite.

[spastorino]

This was automatically closed because I've removed the rewrite branch but ...
I don't think we should add the todo list as a file the same way we don't handle issues in a file inside the project.
We could use something specific for that purpose, what do you think?

[lukaszx0]

Well I can agree with that. So maybe let's create those tasks from list as an issues and add feature label to them. What do you think? I can do that.

Also, great that rewrite is now merged 👍 ✨

[stevenharman]

Did this TODO list ever get converted to Issues? Several items seem to be done, but other are quite unclear. For example:

1. What work remains for JSON API compliance? it's unclear which items need doing vs. what's been done
2. What's the status of a caching solution?

[spastorino]

Hey @stevenharman we are organizing the work for AMS. Current TODO list is here https://www.pivotaltracker.com/s/projects/978898 and current status for JSON API and caching is NOT done. If you come up with a good solution for the problem send a PR and we will evaluate it for inclusion.

[stevenharman]

Ah, great. For the JSON API work, perhaps a good first step would be listing the things that must be done to support it? e.g., even single resources (from a show, for instance) should be in an array, and that we need a simple way to create a links hash full of the various URLs for a resource (perhaps similar to Oat).

Anyhow, I don't want to list them out here, but I can't comment there, and I'm not clear if such discussion is meant to be there, or here in the Github Issues.

[spastorino]

You can start a discussion about this in the rails-api mailing list if you want. 👍