DDragon endpoint error if version() is not specified

[M0kY]

Version:

0.9.1

Steps to reproduce:

The following code, taken from the docs:

kayn.DDragon.Champion.list() // Implicitly targets 8.15.1
    .callback(function(error, champions) {
        console.log(champions)
    })

Expected:

Expected to return an object containing all champions data.

Result:

(node:8844) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'get' of null
    at DDragonRequest.<anonymous> (C:\rito_api\node_modules\kayn\dist\lib\RequestClient\DDragonRequest.js:144:44)
    at Generator.next (<anonymous>)
    at step (C:\rito_api\node_modules\kayn\dist\lib\RequestClient\DDragonRequest.js:18:191)
    at C:\rito_api\node_modules\kayn\dist\lib\RequestClient\DDragonRequest.js:18:437
    at new Promise (<anonymous>)
    at DDragonRequest.<anonymous> (C:\rito_api\node_modules\kayn\dist\lib\RequestClient\DDragonRequest.js:18:99)
    at DDragonRequest.callback (C:\rito_api\node_modules\kayn\dist\lib\RequestClient\DDragonRequest.js:164:21)
    at main (C:\rito_api\index.js:31:6)
    at Object.<anonymous> (C:\rito_api\index.js:62:1)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Function.Module.runMain (module.js:693:10)
    at startup (bootstrap_node.js:191:16)
    at bootstrap_node.js:612:3
(node:8844) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:8844) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

After adding .version('8.15.1') to the initial code the result is the expected champion data.

[cnguy]

Good catch!

This error occurs when the developer is not using a cache (so cache: null). Well, technically, the error occurs because of bad programming by me. I'll release a fix in an hour!

[cnguy]

v0.9.2 has been released with this fix

[M0kY]

Awesome, thank you very much for the quick fix.