-
Notifications
You must be signed in to change notification settings - Fork 9
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
Document endpoint auth methods #451
Conversation
@andrii-balitskyi I'm not sure about the placement and formatting of the note. I think it's important information, but is there a way to present the info. that's not in a hint box? Something like this maybe (but prettier)? |
@DebbieAtSeam sure, but wasn't able to make it look prettier with the current setup. @razor-x any ideas on how to make it look better? |
@andrii-balitskyi I do like that ul better than the hint box, with the exception of the capitalization. Could you please explain a bit more about why users need this info.? For example, why do only some methods accept a client session token? Also, if the ul takes up too much space, you could try it as a plain comma-separated list in a p. Thanks! |
@DebbieAtSeam There are past examples (which I cannot post here) where having this information would have been very helpful to address customer and internal question. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andrii-balitskyi Is there an importance or other logical order to the way in which the auth methods get listed in the bulleted lists? If not, is there a way to display them in alpha order? If not, it's nbd. Thanks!
Thanks, @andrii-balitskyi! |
Closes #447