fix: added _options to topOptions parameters.context.google check

[giorod3]

If _options is not present in the parameters.context.google object then line 78 breaks on getting params from undefined.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[giorod3]

I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[JustinBeckwith]

Thank you! Could you add a double layer of protection here?

Suggested change

	const topOptions = parameters.context.google._options
	const topOptions = (parameters.context.google && parameters.context.google._options)

[giorod3]

do you also want to validate params. as so:
const topOptions = (parameters.context.google && parameters.context.google._options && parameters.context.google._options.params)

[JustinBeckwith]

I don't think that's strictly required here. To be honest I'm surprised there are situations where any of these are null/undefined, but it doesn't hurt to be careful :)

[giorod3]

done, thank you for the prompt response!

[bcoe]

@giorod3 I think you just need to run npm run fix, you appear to be having some TypeScript linting issues, hence the breaking builds.

[giorod3]

@giorod3 I think you just need to run npm run fix, you appear to be having some TypeScript linting issues, hence the breaking builds.

@bcoe we are using this in js. I do not have the command npm run fix. On multiple machines and from multiple users the issue keeps arising. It also happens across all apis, not just one. Once we implement the change, the code works perfect. But we keep having to manually go in and make the change.