Welcome back.

Previously I created a new version of the API and

used resframeworks, view sets and routers.

This allowed me to combine all of my grade views into a single class.

And the router automatically generated the URLs.

I also wrote a custom view method to list coarser views on the course view set.

I still have one problem to solve in this V two implantation though.

My review V sec class extends REST frameworks model views that class.

Which hopefully provides views for creating destroying.

Listing, retrieving and updating reviews.

But since I created that review list view and

a view that lists all the reviews on the site doesn't seem really useful.

I need to get picky about which views this view set provides.

So to start customizing these views, or the view sets rather,

I need to bring in Django REST frameworks mix ins.

Mix ins are, if you're not, if you're like, I know that word, but

I can't know what it is.

Mix ins are a little small classes.

That you mix in to create larger classes.

So it's a way of doing inheritance instead of composition.

We'll talk more about that in later courses.

So. I wanna show you what the model of view

sets class definition looks like.

So we're using this thing here.

I wanna show you what that actually looks like.

So, if I was a do model, view, set and I was working for Jango REST framework.

This is what I would've put in.

So, mixins.CreateModel\ mixin,

mixins.RetrieveModelMixin, mixinUpdatemodelMixin and

destroyModelMixin and, two more,

mixins.ListModelMixin.

And then, the viewsets.GenericViewSet.

And then, pass.

So.

Or I might have passed for now least.

So model view set just a combination of generic view set and

then all of these mix ins, your mix ins come before your

class that they're modifying so that stuff gets evaluated in the right order.

So anyway this is what's normally there.

So the Create model mix in is what handles the creation, the retrieve model mix

in is what handles the retrieving of a single object of a single model instance.

The update is what handles updating a single one,

destroys what handles destroying one and

the list is what handles getting the query set for the full list of them.

So, you can see each one of these things just does one little specific bit.

And then the generic view set is what handles like,

I'm going to make all these views that do this stuff go, right.

So if I want to do all of the stuff but I don't wanna have the list,

it would make sense to just build this again instead of using this.

right?

I got an easier way though, you ready to see the easy way?

Here it comes.

Delete that, rename this to ReviewViewSet, Delete those two lines.

Hey, look at that!

Now I have a model view set that doesn't do lists.

Cuz that's what I want.

So, hey cool!

[LAUGH] We just did it right there, yeah.

Isn't that amazing?

So this should be able to work.

I should be able to go to v2/reviews and method get is not allowed 405 right.

It's not exactly a 404.

It's not like hey that doesn't exist but it's a 405.

The method isn't allowed, I'm not allowed to use get on reviews.

I can't just get a whole list of reviews and

APIs get the 405, then your okay I can't do that.

But if I try to get just one review because I know I have a single

review in there.

I get that actual review, right?

I can get that review, I can put, patch, delete, header, options it.

So, awesome!

Effectively I've created a whole second version of this API.

I wrote less code than I did before.

I think that's pretty impressive.

It's a good idea to look over the documentation for both routers and

view sets, so I put links to both of them in the usual place.

The teachers notes.

At this point you've learned the majority of creating API views with Django REST

framework you started very low level with API view moved up to generic views and

then finished it all off with view sets and routers.

All of these views have been class based views, but

it is possible to create API views with traditional function based views

using some decorators that REST framework provides.

If function based views are more your style.

Check out the teachers notes for a link to the relevant documentation.