Unrecognized OAuth 1.0 signature method: undefined

[robingustafsson]

Running the converter on the example/v2/twitter.json collection gives back this error:

Unrecognized OAuth 1.0 signature method: undefined
Error: Unrecognized OAuth 1.0 signature method: undefined
    at renderHashFunction (/Users/robin/Projects/loadimpact/postman-to-k6/lib/auth/oauth1.js:158:13)
    at new Oauth1Auth (/Users/robin/Projects/loadimpact/postman-to-k6/lib/auth/oauth1.js:40:5)
    at authentication (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/Request.js:101:16)
    at Request (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/Request.js:32:3)
    at Item (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/Item.js:10:3)
    at ListMember (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/ListMember.js:12:5)
    at module.exports.args (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/ListMember.js:1:40)
    at ItemGroup (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/ItemGroup.js:15:5)
    at ListMember (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/ListMember.js:10:5)
    at module.exports.args (/Users/robin/Projects/loadimpact/postman-to-k6/lib/generate/ListMember.js:1:40)

I suppose this is because I have to provide OAuth credentials, but we should have a more helpful error message saying "To convert this collection you'll have to make sure the correct OAuth credentials are included with the collection.". Alternatively we could perhaps allow auth vars to be set as CLI options, something like:

postman-to-k6 example/v2/twitter.json -o twitter.js --oauth1-consumer-key "KEY" --oauth1-consumer-secret "SECRET" ...