interactors icon indicating copy to clipboard operation
interactors copied to clipboard

Platform agnostic interactors

Open taras opened this issue 3 months ago • 1 comments

I'm starting to encounter use cases where I'd like to use Interactors that has nothing to do with DOM.

For example, I have mulitple Kafka messages with very complicated types. I don't need to operate on them, but it would be helpful to be able to select on a kafka topic and match on properties of an event. I would really love the "did you mean one of these?" type feedback when not matching an existing event. I have to implement all of this from scratch without any guardrails.

It would be awesome if I could use the interactors API to represent these objects.

taras avatar Sep 29 '25 17:09 taras

Yes, this is key.

You should be able to supply the matching engine that resolves properties and actions, but the syntax from the client side would be uniform.

Other use cases would be A REST interactor

Posts().create({ author: "bob", content: "Hello Alice" });
Post({ author: "bob", content: matching(/Hello/)}).exists()

We need an interactor definition language that we can use to:

  1. generate a client for communicating with an interactor agent
  2. generate stubs for an interactor agent implementing that schema in typescript, python, etc..

cowboyd avatar Sep 29 '25 17:09 cowboyd