aboutsummaryrefslogtreecommitdiffstats
path: root/src/bin/zot
Commit message (Collapse)AuthorAgeFilesLines
* Re-export the structs from internal modules in the command mod.refactor-cmd-handlingHarald Eilertsen2024-10-302-6/+19
| | | | Just improves usability some.
* Add command module and move implementations to it.Harald Eilertsen2024-10-3010-40/+193
|
* Reenable requesting abook infor for channel.simplifyHarald Eilertsen2024-03-251-2/+17
| | | | Only dumps raw json response for now, make it nicer later.
* bin: A tad nicer stream listing.Harald Eilertsen2024-01-141-1/+1
|
* bin: list channel stream summary in email like styleHarald Eilertsen2024-01-141-8/+14
|
* Additional stream tag types and flags + optional fields.Harald Eilertsen2024-01-141-1/+6
|
* Add high level stream API.Harald Eilertsen2024-01-081-1/+18
|
* Implement channel API's.Harald Eilertsen2023-04-011-5/+30
| | | | | These just output the result as json for now, that's not what we want in the end, but it's where we start.
* Add version API.Harald Eilertsen2023-04-011-0/+7
|
* Another reqrite...Harald Eilertsen2023-03-297-410/+16
| | | | | | | | | | | | | | | | | | 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 Eilertsen2023-03-272-1/+2
| | | | | | | | | 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.HEADmasterHarald Eilertsen2023-03-261-0/+21
| | | | | | | 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.
* Make abook output prettier.Harald Eilertsen2023-03-261-1/+3
| | | | | | Only print the most relevant information from the returned data. Output it as CSV (but we don't do any sort of escaping yet). This will probably not stay this way, but works as a demonstration for now.
* Fetch abook and xchan directly from api.Harald Eilertsen2023-03-264-80/+19
| | | | We don't really need the intermediate layer in the binary module.
* Update reqwest and make async.Harald Eilertsen2021-07-057-22/+25
| | | | | | | | This means adding the full tokio as a dependency. While there isn't much gain to going async in the current cli demo app, a full fledged app may have more to gain by it. First foray into async rust, so I might not do it right...
* bin/zot: Clean up channel stream output somewhat.Your Name2020-05-031-9/+18
| | | | Not really easy to find a goot pure text representation of this, though.
* Promote example app to proper command line client.Your Name2020-05-039-0/+597
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-21 19:05:07 +0000