-
Notifications
You must be signed in to change notification settings - Fork 147
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
feat: load protos from JSON, grpc-fallback support #749
Conversation
Something is wrong here, I need to take a look. |
Codecov Report
@@ Coverage Diff @@
## master #749 +/- ##
=======================================
Coverage 96.46% 96.46%
=======================================
Files 20 20
Lines 2236 2236
Branches 467 467
=======================================
Hits 2157 2157
Misses 24 24
Partials 55 55 Continue to review full report at Codecov.
|
@schmidt-sebastian Just FYI - this PR brings in the new auto-generated code that:
Since tests pass, I'm pretty confident everything is fine, but would like to have your ✅ here anyway. Thank you! |
# Node.js specific cleanup | ||
subprocess.run(["npm", "install"]) | ||
subprocess.run(["npm", "run", "fix"]) | ||
os.chdir("dev") | ||
subprocess.run(["npx", "compileProtos", "src"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also run https://github.com/googleapis/nodejs-firestore/blob/master/dev/protos/update.sh here? That generates our d.ts typings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I guess so (it's unrelated to this particular PR but it's a good place to call any custom scripts after generation).
This LGTM. Just curious if the fallback would also work for streams? |
No, unfortunately it won't work for streaming methods. All other types of calls (unary, LRO, paginatied calls) are supported. |
@alexander-fenster I see some problem when timestamp is processed. While REST call (through fallback as rest) is returning time values as string, protobuf parsers expect it as ITimestamp as per protos.json. Do you see a way to solve this?
I tried changing the firestore_v1_proto_api.js but its not updating as expected. For sure something i'm missing. It will be of great help if you can help on this. |
This PR was generated using Autosynth. 🌈
Here's the log from Synthtool: