-
Notifications
You must be signed in to change notification settings - Fork 211
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
fix: pass Query.wrapIntegers to job.getQueryResults #1191
fix: pass Query.wrapIntegers to job.getQueryResults #1191
Conversation
Resolves issue reported on #6 (comment) |
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.
Overall comment, from your car mechanic telling you it might be time to get an oil change 😹 It might be good for someone to do a PR that's just a pass of fixing up linting errors. It looks like the repo has accumulated a few.
@@ -927,7 +927,7 @@ export class BigQuery extends Service { | |||
'value ' + | |||
value.integerValue + | |||
" is out of bounds of 'Number.MAX_SAFE_INTEGER'.\n" + | |||
"To prevent this error, please consider passing 'options.wrapNumbers' as\n" + | |||
"To prevent this error, please consider passing 'options.wrapIntegers' as\n" + |
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.
I don't know the history of the wrapNumbers vs wrapIntegers, but it won't be a breaking change, right?
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.
I think it was a typo, because the option available to users is wrapIntegers
so this is just fixing it.
Query.wrapIntegers
was being ignored and not passed tojob.getQueryResults
when used inbigquery.query
.