Soc Sieng

> Hi, @socsieng > can you help check with failed build? It seems it was broken several months ago. Looks like it's failing here: https://github.com/google-pay/google-pay-button/runs/6650864917?check_suite_focus=true#step:7:22 > ``` > Checking formatting......

Created https://github.com/google-pay/google-pay-button/pull/143 to fix the prettier issue.

Depends on what you mean by _before my page starts to display_. The `readyToPayChangeCallback` method or `readytopaychange` event can be used to handle the results of the component's internal `isReadyToPay`...

Can you confirm if you get the same issue with the following integration? https://stackblitz.com/edit/google-pay-react?file=src%2FApp.js

Might be able to introduce another input argument like `--random-delay`. Where this value is the number of seconds randomised between `0` and random amount to add to the default delay...

Thanks for putting this PR together. Would love to see it merged. For some reason, installing the package with the following command does not place `prettier` in the `node_modules/.bin` directory:...

Thanks @Lavariet, the install from the pull request did the trick (it's significantly slower to install though... thought that it was broken) ```sh npm i -D prettier/prettier#pull/7111/head ``` FWIW, it...

Can you tell me if the plugin is working as expected? That message shouldn't impact the plugin. I'll release an update soon that will hopefully reduce the amount of noise...

I haven't added any commands to any of the menu items. I'm happy to treat this as a feature request though. In the meantime, you can use the command palette...

I think that reasoning should be more prominent. Suggest moving it above examples.