Consider fetching by default?

[dshemetov]

No description provided.

[capnrefsmmat]

Is there any circumstance where you'd want to manipulate the call object? Or do we anticipate people will run fetch() every single time?

In principle I think our API queries always return the same response for a given input, so I don't see people calling fetch() multiple times on the same call, and that'd be the only other reason I can think of for keeping it separate.

[dshemetov]

One thing I liked about the current interface is that it helps debugging - you can always look at the URL and see if it's been mangled in some way.

We also have the with_base_url() modifier to adjust the base url of a call (e.g. staging API). So another thing that's aimed at development.

[dsweber2]

There's a couple of arguments that can currently get passed to fetch which would need to be integrated into each endpoint, which feels like awkward boilerplate, at least from a package dev perspective. I suppose good use of ... could cover that.

[dshemetov]

After today's discussion, it seems that we're moving forward with this integration using a default args list function fetch_args_list().