Starting from the ItemView, I have finally converted my application to use marionette application at the top. With this, the overall structure has started falling in place.
One benefit of committing to a framework is that it can force you to some good practices. While building my API using Django view, I was constantly using @csrf_exempt decorator so that I don't have to deal with passing the csrf token while making AJAX requests. I said I will come back to it but never did. However with Django Rest Framework, this was not a possibility and so I ended up handling the issue.
One benefit of committing to a framework is that it can force you to some good practices. While building my API using Django view, I was constantly using @csrf_exempt decorator so that I don't have to deal with passing the csrf token while making AJAX requests. I said I will come back to it but never did. However with Django Rest Framework, this was not a possibility and so I ended up handling the issue.
As it turns out, it is surprisingly simple. The CSRF token is included in a cookie by Django whenever csrf protection is on. You just need to extract that cookie and include the CSRF token as a header in request. All the code required to do this is provided in the Django official documentation.
So with CSRF hurdle crossed, I was able to create a new Publication via my Marionette app via the API.
Looks like it is time to go back to DRF and check out the Pages level API.
Looks like it is time to go back to DRF and check out the Pages level API.
No comments:
Post a Comment