Add tags

[vincentvanderweele]

As described in #1, I added support for adding tags to all endpoints of a specific service, like this:

{
  "swagger": "2.0",
  "info": {
    "title": "Swagger Combine Rename Example",
    "version": "1.0.0"
  },
  "apis": [
    {
      "url": "http://petstore.swagger.io/v2/swagger.json"
    },
    {
      "url": "https://api.apis.guru/v2/specs/medium.com/1.0.0/swagger.yaml",
      "tags": {
        "add": [
          "Medium"
        ]
      }
    }
  ]
}

There are of course two places where tags are used: in the schema root and in every operation. I chose to only add these tags to the operation tags because the root tags will all be merged into a single array anyway (so it doesn't make much sense to allow adding tags per service).

I don't handle the case that an added tag already exists because renameTags doesn't handle that either. I also chose to not add a new integration test for this functionality but this can of course be added if needed.

[fabsrc]

Hi Vincent,

thank you for your contribution 😊 This feature really is a great addition to this module.
However there are two things you could improve in your PR:

• Add some documentation to the README.md file
• Check and remove duplicate values in the tags array (e.g. by using lodash's uniq function). If you want to you can do this for the renameTags function as well.

Integration tests are optional, maybe we will add some later.

[vincentvanderweele]

Will do!

Currently I have a problem that an array gets converted to an object with integer keys. I'm not sure if my change is causing this, but if it is, I'll obviously fix that as well in this PR.

[vincentvanderweele]

• fixed the bug and added an extra testcase (earlier I forgot to check if we were really dealing with an operation object, so it could also be the shared parameters).
• added an example to the readme and made that same example an integration test
• removed duplicate tags in renameTags and addTags and added testcases for that