Mezzanine <-> Django-Rest-Framework
511 views
Skip to first unread message
Sanjay Bhangar
Sep 23, 2014, 4:53:52 PM9/23/14
to mezzani...@googlegroups.com
Just moving this discussion to a separate thread from [0]
Stephen, if you (or anyone) have the time to look at my fork on github
and Andrzej Grymkowski's commit [1]: and maybe give a quick opinion
of whether this seems useful to pursue.
Personally, I think for a v1, just making the API read-only maybe
okay? I can try giving this another shot next month or so - my
apologies for not managing to spend some time on this, work has been a
bit more stressful than anticipated (as always :/ )
Cheers,
Sanjay
[0] https://groups.google.com/forum/#!topic/mezzanine-users/BW0Xjn5Zwvg
[1] https://github.com/batpad/mezzanine/commit/025876964e4abe9888eed1ba40fc54a8bd368c0d
Stephen, if you (or anyone) have the time to look at my fork on github
and Andrzej Grymkowski's commit [1]: and maybe give a quick opinion
of whether this seems useful to pursue.
Personally, I think for a v1, just making the API read-only maybe
okay? I can try giving this another shot next month or so - my
apologies for not managing to spend some time on this, work has been a
bit more stressful than anticipated (as always :/ )
Cheers,
Sanjay
[0] https://groups.google.com/forum/#!topic/mezzanine-users/BW0Xjn5Zwvg
[1] https://github.com/batpad/mezzanine/commit/025876964e4abe9888eed1ba40fc54a8bd368c0d
Renyi
Oct 2, 2014, 3:29:53 AM10/2/14
to mezzani...@googlegroups.com
Awesome that someone is actually working on this ! Thank you !
Took a quick glance at the commits, here are some suggestions,
1. Use separate API url for management/administration (Object level / Django permission) and public view (Read Only)
2. Token authentication integration with Mezzanine accounts (for mobile apps, etc.)
3. Default filtering by user(author) / site if applicable
4. Optional integration with https://github.com/marcgibbons/django-rest-swagger
Will contribute more after I have a chance to play around with the codes.
Cheers !
Took a quick glance at the commits, here are some suggestions,
1. Use separate API url for management/administration (Object level / Django permission) and public view (Read Only)
2. Token authentication integration with Mezzanine accounts (for mobile apps, etc.)
3. Default filtering by user(author) / site if applicable
4. Optional integration with https://github.com/marcgibbons/django-rest-swagger
Will contribute more after I have a chance to play around with the codes.
Cheers !
Message has been deleted
Andrzej Grymkowski
Jul 8, 2015, 3:57:04 AM7/8/15
to mezzani...@googlegroups.com
Hi
Since long time ago (almost year!) I updated branch to current version of mezzanine. Travis build passes : )
What more:
+ removed unnessescary dependencies like `markdown` or `django_filters`.
+ added tests for blog posts
+ added methods for list blog posts like number of posts per month, per author or per tags
+ method for get five last posts.
+ added some shortcut to get content from page.
+ added 'browsable api`. Just after installation go after `api/` in browser.
TODO for current features:
- some generic api to manage pages
- docs for blog and pages about `?search=` parameter
- add links with custom methods from blog to browsable api. Now they are not visible. Dont know why
pull request: https://github.com/stephenmcd/mezzanine/pull/1210
best regards
Andrzej Grymkowski
Jul 14, 2015, 1:12:29 PM7/14/15
to mezzani...@googlegroups.com
Can someone review this pull request?
Daniel McLellan
Sep 1, 2015, 8:54:03 PM9/1/15
to Mezzanine Users
bump for code review request
Reply all
Reply to author
Forward
0 new messages