(WIP) feat: JSON Schema generation

[In-line]

1. JSON schema generation
2. Typed response/request protocol

[ilya-zlobintsev]

Could you explain what the use case of JSON schema here might be? Generating type definitions for API clients in other languages?

[In-line]

Yes, plus it's a documentation for API.

…

-------- Original Message --------

On Wednesday, 10/22/25 at 11:07 Ilya Zlobintsev ***@***.***> wrote: ilya-zlobintsev left a comment [(ilya-zlobintsev/LACT#784)](#784 (comment)) Could you explain what the use case of JSON schema here might be? Generating type definitions for API clients in other languages? — Reply to this email directly, [view it on GitHub](#784 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AETPTKBT6SK2RU4SDKUKWTL3Y4ULNAVCNFSM6AAAAACJXAUZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMZQG43TANZRGA). You are receiving this because you authored the thread.Message ID: ***@***.***>

[ilya-zlobintsev]

I have some other ideas about making the API easier to use, I'd like to try them out first, so this PR might sit unreviewed for a while

[In-line]

Sure,let me know. When you would like this to get finished. There are few additional types that need custom spec providers

…

-------- Original Message --------

On Sunday, 10/26/25 at 17:44 Ilya Zlobintsev ***@***.***> wrote: ilya-zlobintsev left a comment [(ilya-zlobintsev/LACT#784)](#784 (comment)) I have some other ideas about making the API easier to use, I'd like to try them out first, so this PR might sit unreviewed for a while — Reply to this email directly, [view it on GitHub](#784 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AETPTKBUPBK4JKKVMGBQTL33ZS63ZAVCNFSM6AAAAACJXAUZHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBYGU2TMNJRG4). You are receiving this because you authored the thread.Message ID: ***@***.***>

[In-line]

@ilya-zlobintsev Hi, do you have any updates?

[ilya-zlobintsev]

@ilya-zlobintsev Hi, do you have any updates?

I had an idea to utilize the varlink IPC protocol for LACT, as it is very similar to the current IPC implementation (JSON over unix sockets), but defined as a standard with the ability to define an interface spec that could easily generate client implementations.

This is still something I would like to do, but there were some questions left to figure out for a prototype, such as varlink vs zlink libraries and coexistence with the current IPC protocol.