-
Notifications
You must be signed in to change notification settings - Fork 9
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
Is this project still active? #9
Comments
No longer active. If I were to do this again I would not do mixins. |
What project(s) would you recommend as a replacement? |
I don't know of any projects as ambitious in delivering a hypermedia abstraction layer. Django rest framework is working on an API driven admin but their hypermedia rendering is hard coded and not a standard. Personally I prefer restless as an API framework for python, but it is just the essentials - no hypermedia out of the box but easy to do. |
Can you expand on the 'would not do mixins' point? What would you have done? |
Mixins was the idea that you could put form logic in one class, crud in another, and presentation in another, and then through complex inheritance you would have a class that does a crud action. Restless views this as an anti-pattern for sanity reasons. I would instead make a standalone layer to keep track of hypermedia meta data that the views can consult during render. Basically opt for a more functional approach. |
Sounds good. Any plans to pursue this (or refactor the current project)? |
A half a year later and I am now kicking off the replacement to this project: Still ended up using some mixins, but at a more sane level. Each mixin has their own separated concerns and do not cross orchestrate super calls. I plan on packaging up a reactjs client to work with the library (but really it will just be a schema JSON CRUD client). But still lots of work to be done. I am sprinting on this for pycon. |
No description provided.
The text was updated successfully, but these errors were encountered: