pull out onChange handler for #input_apiKey so it can be called manually

[alexagranov]

Hi there. One feature clients have really loved is the ability to exercise the API endpoints with a prepopulated ApiKey if the API is protected with one. This comes in really handy for marketing purposes - people can play around in a sandbox environment before going through the process of getting a real ApiKey.

Before the introduction of the ApiKeyAuthorization class, setting the 'apiKey' property when creating SwaggerUi would pre-populate the 'api_key' input and then I just had to use that for generated API calls.

ApiKeyAuthorization is sweet but I'm wondering if we can just pull out the handler for change() on the 'api_key' input so that we can call it after code that sets the 'api_key' value manually? This is needed since the change() event doesn't fire unless focus is lost on an input - which it doesn't have in this case. I left in sample commented-out code that shows this.

What do you think?

[fehguy]

Hi, I think that's reasonable to do. Are you using the default index.html of swagger for your app? I'm wondering if this isn't something that should live in your (custom?) index.html.

[alexagranov]

I'm actually using grape-swagger-ui which just uses index.html as a
template but they pull it from swagger-ui.

Thanks for getting back so fast!
On Sep 20, 2014 12:15 PM, "Tony Tam" [email protected] wrote:

Hi, I think that's reasonable to do. Are you using the default index.html
of swagger for your app? I'm wondering if this isn't something that should
live in your (custom?) index.html.

—
Reply to this email directly or view it on GitHub
#594 (comment).