Where should I give the secret on validation? about jwt HOT 8 CLOSED

ok, sounds good, will try to fix today, thank you for the feedback 👍

from jwt.

I prefer 1 just to reduce copy-paste and for an easier example/test/code maintainability. BTW, I got your point, will push slightly updated README now.

Thanks once more for the feedback 😉

from jwt.

Hi @elgs if you've any suggestions for v2 please add them here :) #39

from jwt.

Hi, this can be done via https://godoc.org/github.com/cristalhq/jwt#Signer (See Verify method). Signing and verifying token is a pure Signer task.

from jwt.

Thanks. It looks like I confused validate and verify. Would be great if you could add a few examples in the readme.md, like:

1. how to turn a JSON string into a jwt string;
2. how to verify a jwt string;

As a user, we don't want to mess with your internal types, unless necessary, in most cases, we start with a raw JSON string, and we expect a jwt string, and for verification, we start with a jwt string and a string typed secret, and expect a boolean answer.

from jwt.

Thank you so much! Last question, it would be great if you could put an example of verify in the readme.md.

from jwt.

@elgs but there is already a full example in example files (there are links in README.md)

from jwt.

The links only says build, parse, validate in the README.md, with your instruction, I figured how to get things done. There are two types of people:

1. if there's example in the code, why would I bother to write them in README.md;
2. if I could put examples in README.md, why would I bother users to read the code;

I fully respect each of styles. So it's fine to keep the examples in the code. Thank you so much!

from jwt.