Skip to content
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

API information empty #57

Closed
Laptopmini opened this issue Feb 12, 2016 · 3 comments
Closed

API information empty #57

Laptopmini opened this issue Feb 12, 2016 · 3 comments

Comments

@Laptopmini
Copy link

I am currently having this issue where some of the APIs have empty parameters and are classified in a group called None.

Here is a screenshot: http://i.imgur.com/2pXFhLj.png

Here are the APIs that seem to be incompatible:
url(r'^api-token-auth/', rest_views.obtain_auth_token),
url(r'^api/v1/auth/login/$', LoginView.as_view(), name='login'),
url(r'^api/v1/ios/auth/login/$', LoginView.as_view()),
url(r'^api/v1/auth/logout/$', LogoutView.as_view(), name='logout'),
url(r'^api/v1/ios/auth/logout/$', LogoutView.as_view()),

Also, is there a way to create "Groups" of APIs manually to organize the page more?

Many Thanks!

@manosim
Copy link
Owner

manosim commented Feb 13, 2016

Hello @Laptopmini!

About the files missing: Are you using APIViews? If so I think it is not possible for DRF Docs to pickup the fields. Maybe in the near future you will be able to pass the fields in the docstring!

Currently it is not possible to create Groups manually. I am planning to fix some really important bugs (ModelViewSets etc) so I guess we can leave this one for a later stage?

@debnet
Copy link

debnet commented Feb 29, 2016

Fixed in #70.

@choi-hye-min
Copy link

이 문제의 답을 찾고 있었습니다.
아직 계획중이군요

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants