You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Other mainstream documentation frameworks provide a simple UX trick when Basic HTTP Auth is required on an endpoint, where the user can input a username and a password instead of the serialized token.
The username and passwords are then serialized as base64("username:password") and sent along with the request.
Describe the solution you'd like
I would be nice for Fumadocs to include this little change, although not strictly necessary.
Or at least make it possible to customize the renderCustomField function.
Describe alternatives you've considered
I tried patching the APIPlayground component but it would require extensive work due to it not being made with this functionality in mind. Please let me know if there are other alternatives.
Additional context
No response
The text was updated successfully, but these errors were encountered:
What problem will this feature address?
Other mainstream documentation frameworks provide a simple UX trick when Basic HTTP Auth is required on an endpoint, where the user can input a username and a password instead of the serialized token.
The username and passwords are then serialized as
base64("username:password")
and sent along with the request.Describe the solution you'd like
I would be nice for Fumadocs to include this little change, although not strictly necessary.
Or at least make it possible to customize the renderCustomField function.
Describe alternatives you've considered
I tried patching the APIPlayground component but it would require extensive work due to it not being made with this functionality in mind. Please let me know if there are other alternatives.
Additional context
No response
The text was updated successfully, but these errors were encountered: