Documentation of getAccessToken appears incorrect

[mattgrande]

I wanted to verify what I'm seeing is correct before issuing a PR.

In the documentation for getAccessToken, the return value is specified as being optional; see here (at least that's what I interpret [accessTokenExpiresAt] being surrounded as square brackets as meaning).

However, in the validateAccessToken function, it ensures that the token is present.

So, what is incorrect, the documentation or the implementation?

(And please let me know if I'm misinterpreting something)

[maxtruxa]

Looks like the documentation was correct, until 789db64 changed the behavior.

Edit:
Actually, looking at the change again.. before that commit the first check was broken:

if (!accessToken.accessTokenExpiresAt && !(accessToken.accessTokenExpiresAt instanceof Date)) {

But instead of fixing it, access tokens without an expiry were disallowed completely.

So for now this is a bug with the documentation.

[maxtruxa]

Fixed by #491

[mattgrande]

Thanks @maxtruxa!