Skip to content
This repository has been archived by the owner on Mar 29, 2019. It is now read-only.

should we consider dropping imago? #82

Open
jamesturk opened this issue Feb 21, 2017 · 2 comments
Open

should we consider dropping imago? #82

jamesturk opened this issue Feb 21, 2017 · 2 comments

Comments

@jamesturk
Copy link
Member

are others using imago?

I don't think we're likely to use this for Open States' new API, in large part b/c this is based on https://github.com/dobarkod/django-restless which hasn't seen an update in ~2 years. (we went down this road w/ django-piston, leading to a fair amount of regret)

Probably about equally feature-complete I have https://github.com/openstates/ocd-jsonapi/ which is based on django-rest-framework (a well supported & maintained library) and which is compatible with the http://jsonapi.org/ spec. I'm not sure if we'll go that route either but I figured I'd mention it as an option.

(I'm also somewhat interested in exploring something GraphQL inspired for Open States API v2, if that is of interest to anyone else)

@fgregg
Copy link
Contributor

fgregg commented Feb 21, 2017

We are using imago, but don't have a great deal of affection for it.

@jpmckinney
Copy link
Member

I don't use imago. We could probably lighten some docs at http://docs.opencivicdata.org/ if we drop it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants