Skip to content

RPC... #6187

@progman1

Description

@progman1

with regard to #6159 the docs still say:
"Definitions of available requests, notifications, and their associated types"

the mli file pointed to says
"Implementation of the protocol used by dune rpc. Independent of IO and any specific rpc requests. "

this is a contradiction, no?
the response to #6146 was that the mli was the best available document
which probably means excepting the source code.
so I've been rummaging through the code and made some minor progress with src/dune_rpc/dune_rpc_impl.
is this the 'usable client' mentioned in readthedocs?
I'm having a hard time extricating it from the build context of dune as a whole. I am also looking at test/expect-test/dune_rpc/dune_rpc_e2e but seemingly dependent on the former.
perhaps struggling is good for the soul but in this moment of weakness I will ask: is there a more 'useable' standalone client implementation
available, a demo/skeleton?

after all, the mli says:
" The protocol described here is stable and is relied
on by 3rd party clients."
3rd parties = JST teams only?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions