You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to extend a client with one that's already been compiled? For example, if I have some package "B" that depends on "A", and in "B" there is a Common interface. If I wanted to create a Service interface for package "A" that also has the functionality of the Common interface, is there any way of doing so with only access to the generated code from "B" (not the .capnp definitions)?
In this scenario, there is no shared logic between those interfaces (as in, either could function independently of the other).
The text was updated successfully, but these errors were encountered:
See #233. At schema-compilation time, capnp compile needs to be able to find the .capnp files of all types being referenced. So you are going to need to give it access to the .capnp files from package B.
Similar question to #261:
Is it possible to extend a client with one that's already been compiled? For example, if I have some package "B" that depends on "A", and in "B" there is a
Common
interface. If I wanted to create aService
interface for package "A" that also has the functionality of theCommon
interface, is there any way of doing so with only access to the generated code from "B" (not the.capnp
definitions)?In this scenario, there is no shared logic between those interfaces (as in, either could function independently of the other).
The text was updated successfully, but these errors were encountered: