| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Only dumps raw json response for now, make it nicer later.
|
| |
|
|
| |
Also reenables the relevant tests.
|
| |
|
|
|
| |
These just output the result as json for now, that's not what we want in
the end, but it's where we start.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Third time must be where it sits I hope.
I felt the API was getting a bit too distracted by unnecessary
constructs and abstractions, so I'm trying to simplify it by making it
more straight forward.
The idea now is to have one main API class (ZotApi), and all the various
remote API's as public methods on this basic class. Iow, the ZotApi
class is mainly based on the existing `Client` class, which is then
being phased out.
And instead of having each API tied to the data type they return, I'm
just adding methods that will return the respective data types. This
should reduce coupling between the returned data, and the API calls
themselves.
|
| | |
|
|
|
The idea is to try to generate more of the boilerplate code, but for now
we only do the `z()` method definition. There are also some we're not
quite able to replace yet (like XChanRequest) since it also has life
times.
It's a start anyways :)
|
