@@ -377,7 +377,7 @@ This gem is tested against MRI, JRuby, and Truffleruby.
377
377
Each of those has varying versions that target a specific version of MRI Ruby.
378
378
This gem should work in the just-listed Ruby engines according to the targeted MRI compatibility in the table below.
379
379
If you would like to add support for additional engines,
380
- see ` gemfiles/README.md ` , then submit a PR to the correct maintenance branch as according to the table below.
380
+ see [ gemfiles/README.md] ( gemfiles/README.md ) , then submit a PR to the correct maintenance branch as according to the table below.
381
381
</details >
382
382
383
383
<details >
@@ -404,25 +404,25 @@ of a major release, support for that Ruby version may be dropped.
404
404
| 3️⃣ | older | N/A | Best of luck to you! | Please upgrade! | |
405
405
406
406
NOTE: The 1.4 series will only receive critical security updates.
407
- See [ SECURITY.md] [ 🚎sec-pol ]
407
+ See [ SECURITY.md] [ 🔐security ] .
408
408
409
409
## Usage Examples
410
410
411
411
### Global Configuration
412
412
413
- If you started seeing this warning, but everything is working fine, you can now silence it.
414
- ``` log
415
- OAuth2::AccessToken.from_hash: `hash` contained more than one 'token' key
416
- ```
413
+ You can turn on additional warnings.
417
414
418
415
``` ruby
419
416
OAuth2 .configure do |config |
420
- config.silence_extra_tokens_warning = true # default: false
421
- config.silence_no_tokens_warning = true # default: false, if you want to also silence warnings about no tokens
417
+ # Turn on a warning like:
418
+ # OAuth2::AccessToken.from_hash: `hash` contained more than one 'token' key
419
+ config.silence_extra_tokens_warning = false # default: true
420
+ # Set to true if you want to also show warnings about no tokens
421
+ config.silence_no_tokens_warning = false # default: true,
422
422
end
423
423
```
424
424
425
- This comes from ambiguity in the spec about which token is the right token.
425
+ The "extra tokens" problem comes from ambiguity in the spec about which token is the right token.
426
426
Some OAuth 2.0 standards legitimately have multiple tokens.
427
427
You may need to subclass ` OAuth2::AccessToken ` , or write your own custom alternative to it, and pass it in.
428
428
Specify your custom class with the ` access_token_class ` option.
0 commit comments