Feature: Adds api response logging.

[rimian]

This adds a logger configuration option. This is helpful for debugging mysterious failures.

It requires the logger respond to :info.

    Recaptcha.configure do |config|
      config.site_key              = '0000000000000000000000000000000000000000'
      config.secret_key            = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
      config.enterprise_api_key    = 'ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'
      config.logger = Logger.new(STDOUT) # or Rails.logger
    end

Pre-Merge Checklist

sorry, I haven't written this... should I put it in "next"?

• CHANGELOG.md updated with short summary

[grosser]

not a fan of the indirection and duplicated logic
prefer something like:

Recaptcha.configuration.logger&.info success: success, reply: reply, event: "recaptcha-response"

[grosser]

also would help to pull the with_reply logic into this method so we always have the reply and can log it

[rimian]

I moved the method to use reply. It does some tagging too.

[grosser]

not sure if that is even needed, users can request with_reply: true and then do their own logging ?

[rimian]

not sure if that is even needed, users can request with_reply: true and then do their own logging ?

Oh, I might give that a go... thanks!

[rimian]

not sure if that is even needed, users can request with_reply: true and then do their own logging ?

I was finding it hard to debug our implementation of this. We are using a logger but when exceptions are raised, it gets a bit fiddly. I just wanted the gem to log responses from the API and I could just forget about it.

[grosser]

does #402 work ?