Feature/update swagger host

[marla-singer]

Closes #1360

Testing api Key authorization

1. Add Swagger file which is supported Authorization. For example http://petstore.swagger.io/v2/swagger.json
2. Go to API details and click on button "Get API Key"
3. Go to Documentation tab and click on button "Authorization"
4. Popup will be showed as on screenshot, field "value" contains the value of api key.
   If it doesn't happen, close popup and open again.
   

[jykae]

Reviewing

[jykae]

@marla-singer Rendering stuck Added first Swagger, then Proxy backend

[marla-singer]

@jykae Describe please your steps

[marla-singer]

@jykae Also ping me if you face this issue #1588 (it'll be great if you can describe to me when this issue is appeared because I can't catch it)

[jykae]

This is possible related to issue:

Coming from Swagger UI utils:

Cannot parse securityDefinitions :/ I try one simpler without those if same issue.

[marla-singer]

@jykae It could be problem with node packages version. Can you please delete the folder "node_modules", run npm i and try again?

[jykae]

Loaded with this: https://github.com/OAI/OpenAPI-Specification/blob/master/examples/v2.0/json/petstore-expanded.json

[marla-singer]

@jykae It's work correct on my side

@jykae It could be problem with node packages version. Can you please delete the folder "node_modules", run npm i and try again?

Please try these recomendation

[marla-singer]

@jykae I found another problem. I'll write you after fixes

[jykae]

Looks like it is basically built right.

Did npm package updates.

[marla-singer]

@jykae Test please with api key too. I pushed fixes

[jykae]

@marla-singer do you have steps how it should work with swagger?

[marla-singer]

@jykae Add steps on PR description

[jykae]

Cool, it works! :)

[jykae]

@marla-singer Also eslint your code for "swaggerUiContent.js" for example.
We have recently started to require it in PRs. In our architect @brylie 's words "Fix at least some errors." As our .eslintrc is not yet fully proper, but we are going towards better code step by step.

After some eslinting I think this is ready to merge.

[marla-singer]

@jykae lint. However I don't know what to do with problems like "Template is not defined", "Meteor is not defined", "Unexpected dangling '_' in '_id' "

[jykae]

@marla-singer If you are using eg. Atom you can click those errors and it opens to browser a page about error and examples how to correct.

Eg. How to fix undefined classes & variables:

import { Meteor } from 'meteor/meteor';
import { Template } from 'meteor/templating';

Clicking "no-undef" would give link: http://eslint.org/docs/rules/no-undef

There are some cases we need to allow in our rules like underscore-dangle in front of "id" that our DB objects use. If you find that kind of case that does not make sense, you can provide a fix to .eslintrc or just note reviewer so that it will eventually end up to allow if agreed so by higher orders :)

Is it ok to fix those import things? Then I merge this in.

[marla-singer]

@jykae Thank for your recommendations! I finished it