Sorry for being out of communication for so long. I can look into the error
in the near future.

The issue is the usual deal where you can't just use a reference to a
method as a callback because uses of this in the method would end up
getting the value null - unless the methods are specially bound to an
object instance for each object that is instantiated.

The provided implementation of ApiClient does not have this problem because
it defines methods in the class constructor, where the new object is in
scope. But a custom API client implementation might not dynamically assign
methods at object creation time. In those cases methods must be invoked
with the context of their API client instance.

In particular, this kind of effect:

call(apiClient.fetch, ...args)

should change to this form:

apply(apiClient, apiClient.fetch, ...args)

On Thu, Aug 4, 2016, 2:44 AM Devin Howard notifications@github.com wrote:

Reopened #4 #4.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
#4 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAllqU1gmpMQJuuZirlqTrkBBO-p_iOks5qcbSNgaJpZM4IkJRh
.

Change call to apply when invoking ApiClient #4

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions