| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Another reqrite... | Harald Eilertsen | 2023-03-29 | 1 | -20/+3 |
| | | | | | | | | | | | | | | | | | | | 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. | ||||
| * | Add ZotAPI trait and derive macro. | Harald Eilertsen | 2023-03-27 | 1 | -8/+3 |
| | | | | | | | | | | 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 :) | ||||
| * | Implement "verify" API.HEADmaster | Harald Eilertsen | 2023-03-26 | 1 | -0/+161 |
| The verify API call returns a full channel object, including the corresponding xchan. I've added the xchan as a field in the Channel object, instead of having all the fields in one object like it is returned from the API. | |||||
 |
index : rust-zotapi.git | |
| Zot API wrapper in Rust. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |