-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clients should remain Scala.js compatible #21
Comments
Interesting findings by @calvellido :) |
@juanpedromoreno could you clarify how this issue relates to #73? Thanks! |
As we will be deriving HTTP services with its auto-derived clients, those will be Scala.js compatible, so likely this issue could be closed once we get the HTTP features. |
@juanpedromoreno, @raulraja is it correct to understand this task is about
Please advise in these respects and also what it is necessary to bridge the gap to become able to actually call Trying to confirm that |
@SemanticBeeng Thanks for bringing all these questions up. Side note: We are not using ScalaPB to convert the idl into the http clients. I hope this answers your questions. |
Thank you for following up. |
Dup of #593 |
We should split the
rpc
core in order to make the client part compatible with Scala.js.The text was updated successfully, but these errors were encountered: