Broken JS bindings #1403
-
|
Let me just say that I have no idea why you broke the most basic thing: creating new objects. Are we supposed now to use Is there a reason for this change? We use Protobuf objects all over our application, and this breaks literally EVERYTHING. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
If you want to have an idea why we did this, check out our blog post: https://buf.build/blog/connect-es-v2 Ultimately, we needed to update connect-es to support protobuf-es v2, which has it's own blog post here: https://buf.build/blog/protobuf-es-v2 We needed to update protobuf-es to v2 to support Protobuf Editions (which Google released). To help easy your migration to connect-es v2, we wrote a comprehensive migration guide as well as automated tooling to help: https://github.com/connectrpc/connect-es/blob/main/MIGRATING.md Hope that helps. |
Beta Was this translation helpful? Give feedback.
If you want to have an idea why we did this, check out our blog post: https://buf.build/blog/connect-es-v2
Ultimately, we needed to update connect-es to support protobuf-es v2, which has it's own blog post here: https://buf.build/blog/protobuf-es-v2
We needed to update protobuf-es to v2 to support Protobuf Editions (which Google released).
To help easy your migration to connect-es v2, we wrote a comprehensive migration guide as well as automated tooling to help: https://github.com/connectrpc/connect-es/blob/main/MIGRATING.md
Hope that helps.