Sha256: 3ef3481b89f8fabe92ec0c57e000dce7c15511f868428d82332b6489ed6395eb

Contents?: true

Size: 972 Bytes

Versions: 12

Compression:

Stored size: 972 Bytes

Contents

You can assign a logger to any instance of operation/scope.

As a rule you would do this assignment to the initialized client:

```ruby
client = CatsClient.new(token: "foobar")
log    = StringIO.new
logger = Logger.new log
```

The client will publish debag messages to the log every time it sets instance of scope/operation schema, or initializes them with some options. Requests and responses are logged at the info level.

Later you can check the log:

```ruby
client.cats.fetch id: 83

log.string
# D, [2017-07-30T22:23:50.262734 #23474] DEBUG -- CatsApi.cats: initializing with options {}...
# D, [2017-07-30T22:23:50.263240 #23474] DEBUG -- #<CatsApi.cats:0x000000034d2710 @token="foobar"> initialized
# D, [2017-07-30T22:23:50.262734 #23474] DEBUG -- CatsApi.cats.fetch: initializing with options {"token"=>"foobar", id"=>83}...
# D, [2017-07-30T22:23:50.263240 #23474] DEBUG -- #<CatsApi.cats.fetch:0x000000034d2840 @token="foobar", "id"=83> initialized
# ...
```

Version data entries

12 entries across 12 versions & 1 rubygems

Version Path
evil-client-3.2.0 docs/helpers/logger.md
evil-client-3.1.0 docs/helpers/logger.md
evil-client-3.0.4 docs/helpers/logger.md
evil-client-3.0.3 docs/helpers/logger.md
evil-client-3.0.2 docs/helpers/logger.md
evil-client-3.0.1 docs/helpers/logger.md
evil-client-3.0.0 docs/helpers/logger.md
evil-client-2.1.1 docs/helpers/logger.md
evil-client-2.1.0 docs/helpers/logger.md
evil-client-2.0.0 docs/helpers/logger.md
evil-client-1.1.0 docs/helpers/logger.md
evil-client-1.0.0 docs/helpers/logger.md