-
-
Notifications
You must be signed in to change notification settings - Fork 321
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
Injecting API Key in built document #203
Comments
I wonder if changes in both
What do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had opened an issue in the Shins project along these lines, but felt it might be better(?) considered here. Mermade/shins#53
To state the scenario from that issue:
Once a user is logged into our site, I'd like to be able to inject a user's API key dynamically into the API calls within the documentation. I'm using Widdershins to generate the base docs from OpenAPISpec, and wondering if I would need to add a div/id into the generated Markdown, and then have some custom JS in Shins to accomplish this.
I started experimenting with this approach, but I realized that because many of the places I'd like to inject the user's API Key value are code fenced, I don't see a way that JS within the shins site would have easy access to that element I was considering adding.
Didn't know if any JS wizards in this project might have a suggestion...
The text was updated successfully, but these errors were encountered: