Fix: all API keys are correctly added when importing OpenAPI collection

[Nithishvb]

Description

Fixes: #2254

This PR addresses the issue where only one API key was being added to the collection when importing OpenAPI collection that contain multiple keys. The fix ensures that all API keys are correctly included during the import process.

Contribution Checklist:

• The pull request only addresses one issue or adds one feature.
• The pull request does not introduce any breaking changes
• I have added screenshots or gifs to help explain the change if applicable.
• I have read the contribution guidelines.
• Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

[TheBlackReverand]

Hello,
With this line you generate a duplicated variable name, so you need to rework your collection after import.
Maybe a param.name in camelCase can do it?

value = '{{' +
   param.name
             .replace('x-', '')
             .replaceAll('-', ' ')
             .replace(/(?:^\w|[A-Z]|\b\w|\s+)/g, function(match, index) {
                  if (+match === 0) return ""; // or if (/\s+/.test(match)) for white spaces
                  return index === 0 ? match.toLowerCase() : match.toUpperCase();
              })
 + '}}';

[Nithishvb]

Hey , could you please explain how this code generate a duplicated variable name?

[TheBlackReverand]

Ok I apologize it's a mistake, I make confusion on ".name"

"securitySchemes": {
      "apiKey1": {
        "type": "apiKey",
        "name": "x-api-key-1",
        "in": "header"
      },
      "apiKey2": {
        "type": "apiKey",
        "name": "x-api-key-2",
        "in": "header"
      }
    }

I thought you use this "name" (with x-api-key-1 / 2) but not.

I checkout your branch and that work fine! I waiting for this merge, I need this fix to :)

Thanks

[mastazi]

@TheBlackReverand @Nithishvb any news on this PR? Has it been approved?