@ezmiller back when I was doing the first iteration of the JSON-API implementation, there was little in libs out there and I settled with marshmallow-jsonapi for that reason. but looking around now, I see so much better stuff. I’ll check out and play with http://ripozo.readthedocs.org/en/latest/ and maybe rebuild our backend with that.
it seems much more straight forward and mature.
but first, I’ll finish the persona branch – which extended its scope quite a bit and contains a complete overhall of the access control, too.
I’ve started to write all of that up in the docs – internal docs were still very much missing. Would love to have your input on it
Hi Ben. Will write you soon. Finally had a talk with the sushi people. Will tell you about it soon.
sure, no worries. I know you have other things going on :)
A few things :)
Does what you said above regarding the re-implementation of the JSON-API mean that I hsould not move forward with that piece.
I mean the part about getting the /latest view to work.
Sounds like it might
I might be interested in working on that backend rebuilt if it makes sense.
no, move ahead with the /latest – we need to have that fixed either way
and replacing the JSON-API is easily a longer task, as we do a bunch of things (remember the polymorphism and the MorphingScheme?) that aren’t the usual way and thus are not supported out of the box by any.
it would require some tinkering and experimenting and figuring out what could be done and whether it would be of any benefit over the current system
and then implementing the missing pieces. that is easily weeks of work in total.
and I think I want to focus on building trellis/techtalks after being done with the persona stuff
thanks for the email about Sushi. Any plans of action/things you’d want to discuss?
Gosh. the more I write about the new persona system, the more I love it.
it solves so many shitty problems, that even google docs doesn’t seem to have quite figured out.