Thanks for getting back to me so soon! Since all my API's have set an Admin only permission, I had to pass 'public=True' to the Schema creation function for them to show up. Hope that can help out someone stuck with this.
Hi Xander. You are doing a fantastic job with Django. Thank you for your effort. I'm still waiting for your django celery course. When can we expect it? Celery is a must for a django developer to get a job.
Thank you. I am drawing out a course path for Celery. In all honesty, I keep swapping around my workload. It is moving forward. It is definitely, like you said, an important topic which needs more attention. I can't give you an eta at the moment.
Hi.. great content.. how can we add authentication to access the api docs if I am using djoser for authentication of the project? Maybe some Login page for using username and password to redirect to api docs?
im getting this error: assert False, f'ReadOnlyField target "{field}" must be property or model field' AssertionError: ReadOnlyField target "ReadOnlyField()" must be property or model field,ive searched high and low for a solution its not anywhere
Hi great tutorial like always, can we do some tasks in swagger ? like hide schema, and add custom help text for each api so user could know more about api, and we can show some common error status code so they know what kind of responses they are going to get using specific api. if we can't modify it too much, which way is more appropriate to build custom api docs with swagger functionalities
There is much that can be done with Swagger in terms of customization, a course in itself. First, take a look at docstring, stackoverflow.com/questions/3898572/what-are-the-most-common-python-docstring-formats. Google format can be popular approach. This info would then be added to the endpoints.
How do you decouple those sensitive endpoints from the rest of the project when pulling this code to prod? It would be great to NOT have all this in the same project, but rather keep API docs separate, otherwise it's a huge security breach when this API is not public and you need Swagger only for testing purposes, e.g. while doing initial manual QA. After manual QA this code should not be part of the project, therefore it's better for it not being the part of the project from the beginning.
Hi, I've done this process several time and today I did for a personal project but the API doesn't display the methods according to his own Model but instead show all the methods under the name of "api", what could I have done wrong?
@@prathameshh27hey there! I actually did but it wasn’t because I found some sort of guidance in DRF, I just separated the URLs that I had for the api, I didn’t put API at the beginning of the url but the class/ anything that can classify what you need to. For example, a full display of API for toys I made the toys/create toys/update and other poll/create poll/update you understand what I mean?
![Swagger documentation for REST API . Django rest framework project tutorial6]](http://i.ytimg.com/vi/XOB-aHKu6e4/mqdefault.jpg)
I have started Swagger successfully with it. Thank you, very useful.
Спасибо вам, дай бог вам здоровья!
Согласен, парень молодец, всё доходчиво объяснил и показал
Fantastic as always 🙌
Please help me with this simple but impassable difficulty: How do I generate the schema publicly for APIs that even have permission enforced? Thanks.
Hi Matt, can you explain further please.
Thanks for getting back to me so soon! Since all my API's have set an Admin only permission, I had to pass 'public=True' to the Schema creation function for them to show up. Hope that can help out someone stuck with this.
Very Useful...👍
Hi Xander. You are doing a fantastic job with Django. Thank you for your effort. I'm still waiting for your django celery course. When can we expect it? Celery is a must for a django developer to get a job.
Thank you. I am drawing out a course path for Celery. In all honesty, I keep swapping around my workload. It is moving forward. It is definitely, like you said, an important topic which needs more attention. I can't give you an eta at the moment.
Nice tutorial. Thanks
Hi.. great content.. how can we add authentication to access the api docs if I am using djoser for authentication of the project? Maybe some Login page for using username and password to redirect to api docs?
im getting this error:
assert False, f'ReadOnlyField target "{field}" must be property or model field'
AssertionError: ReadOnlyField target "ReadOnlyField()" must be property or model field,ive searched high and low for a solution its not anywhere
Hi great tutorial like always, can we do some tasks in swagger ? like hide schema, and add custom help text for each api so user could know more about api, and we can show some common error status code so they know what kind of responses they are going to get using specific api.
if we can't modify it too much, which way is more appropriate to build custom api docs with swagger functionalities
There is much that can be done with Swagger in terms of customization, a course in itself. First, take a look at docstring, stackoverflow.com/questions/3898572/what-are-the-most-common-python-docstring-formats. Google format can be popular approach. This info would then be added to the endpoints.
@@veryacademy checked, thank you for sharing. looking for more videos on it from you.
@@veryacademy I need a course sir
How do you decouple those sensitive endpoints from the rest of the project when pulling this code to prod? It would be great to NOT have all this in the same project, but rather keep API docs separate, otherwise it's a huge security breach when this API is not public and you need Swagger only for testing purposes, e.g. while doing initial manual QA. After manual QA this code should not be part of the project, therefore it's better for it not being the part of the project from the beginning.
You can control that at the gateway level. You could also require username and password to access specific routes
Hi, I've done this process several time and today I did for a personal project but the API doesn't display the methods according to his own Model but instead show all the methods under the name of "api", what could I have done wrong?
I am seeing the same problem. Did you find a solution to this?
@@prathameshh27hey there! I actually did but it wasn’t because I found some sort of guidance in DRF, I just separated the URLs that I had for the api, I didn’t put API at the beginning of the url but the class/ anything that can classify what you need to. For example, a full display of API for toys I made the toys/create toys/update and other poll/create poll/update you understand what I mean?
hey make a video on django deployment in vps plz ?.
Is there a link to the project github?
Why are we not using `django-rest-swagger`?
Err we are?
it has been archived
Thank you
You're welcome
Teach how to make restapi on django .and how to apply on project in company
Thank you for the suggestion.