HMAC section of README outdated

[boardfish]

This section of the README has the following code:

hmac_secret = 'my$ecretK3y'

token = JWT.encode payload, hmac_secret, 'HS256'

# eyJhbGciOiJIUzI1NiJ9.eyJkYXRhIjoidGVzdCJ9.pNIWIL34Jo13LViZAJACzK6Yf0qnvT_BuwOxiMCPE-Y
puts token

decoded_token = JWT.decode token, hmac_secret, true, { algorithm: 'HS256' }

# Array
# [
#   {"data"=>"test"}, # payload
#   {"alg"=>"HS256"} # header
# ]
puts decoded_token

# Without secret key
token = JWT.encode payload, nil, 'HS256'

# eyJhbGciOiJIUzI1NiJ9.eyJkYXRhIjoidGVzdCJ9.pVzcY2dX8JNM3LzIYeP2B1e1Wcpt1K3TWVvIYSF4x-o
puts token

decoded_token = JWT.decode token, nil, true, { algorithm: 'HS256' }

# Array
# [
#   {"data"=>"test"}, # payload
#   {"alg"=>"HS256"} # header
# ]
puts decoded_token

In particular, this line causes issues: decoded_token = JWT.decode token, nil, true, { algorithm: 'HS256' }

At the time of writing, this was probably fine, but now it raises a JWT::DecodeError: No verification key available.

[boardfish]

There may be other sections of documentation that suffer from this too.

[anakinj]

Thanks for noticing. Think something changed a few versions back. Maybe I'll remove the whole example from the readme, it does not make sense to use an empty string as secret when signing the payload.

[boardfish]

I've opened a PR to do so if it makes sense to. Hope that helps!

I'm also happy to check the rest of the README examples and make sure they're up to scratch.