-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Please add V3 to Google Jobs #1292
Comments
We just need to run the generator. @kinwa91 maybe you could take a crack at this :) Just run |
@JustinBeckwith @kinwa91 has this been resolved yet, I just discovered this one? I actually fixed my first issue of usign the nodejs module with AWS Lambda for a job searching API i'm building because I wasn't uploading and pointing to the JSON file for
I see this PR is open. I understand its Sunday and you're probably busy so I'm curious how I can make this work on my end if the PR is going to take some time to integrate. Thanks for your time! |
Sorry for one last message on this thread, its unclear to me if this is related to me using v2 for right now but in Cloudwatch I see this spit out by the node module when trying to use v2:
This Edit: i wanted to also add the output of printing out the authClient from my lambda script, in case its helpful:
Basically it seems like even though I'm setting up |
Greetings folks - this is out! |
awesome thanks @JustinBeckwith ! Sadly, our client ended up cancelling the project I needed this for but its awesome that you've been so prompt and helpful. |
Thank you for updating with V3!!! |
Using version latest version 32.0.0 here: https://www.npmjs.com/package/googleapis
Documentation / Code example states that we should be using V3 of the api here: https://cloud.google.com/talent-solution/job-search/docs/before-you-begin
After installing googleapis and trying the example snippet I get
Further investigation has shown me that in /node_modules/googleapis/build/src/apis/jobs/index.js has specified:
Please include support for v3.
Thanks!
The text was updated successfully, but these errors were encountered: