3 Commits

Author	SHA1	Message	Date
Christian Banse	895749e449	Starting `v5` development ... This commit serves as the basis for further `v5` developments. It will introduce some API-breaking changes, especially to the way tokens are validated. This will allow us to provide some long-wanted features with regards to the validation API. We are aiming to do this as smoothly as possible, however, with any major version. please expect that you might need to adapt your code. The actual development will be done in the course of the next week, if time permits. It will be done in seperate PRs that will use this PR as a base. Afterwards, we will probably merge this and release an initial 5.0.0-alpha1 or similar.	2022-08-27 11:40:20 +02:00
Michael Fridman	4426925f0c	CI check for Go code formatting (#206) ... Signed-off-by: jay-dee7 <jasdeepsingh.uppal@gmail.com> Co-authored-by: jay-dee7 <jasdeepsingh.uppal@gmail.com>	2022-05-28 16:03:15 +02:00
hyeonjae	e01ed05a31	remove unnecessary for loop in token signing string for readability (#34) ... * remove unnecessary for loop in token signing string for readability - add testcase - add benchmark - improve performance slightly * Fix benchtests on token_test.go * Update token_test.go to v4 Co-authored-by: hyeonjae <hyeonjae@ip-192-168-1-3.ap-northeast-2.compute.internal> Co-authored-by: Luis Gabriel Gomez <lggomez@users.noreply.github.com>	2022-02-03 08:47:58 -03:00