@lbalmaceda @martinoconnor Please review at your free time.
If there is a board or group of people that I should include, please let me know. thanks.

The added withClaim() method is not type safe, and it is not possible to overload it due to type erasure. Also, nested collections would be raw types, so there would be no guarantee as to the types they would contain.

A reasonable compromise may be to accept only primitive wrapper types, Sets and Lists and to call toString() on anything else. That would require instanceof checks at runtime which may be ugly.

The added withClaim() method is not type safe, and it is not possible to overload it due to type erasure. Also, nested collections would be raw types, so there would be no guarantee as to the types they would contain.

A reasonable compromise may be to accept only primitive wrapper types, Sets and Lists and to call toString() on anything else. That would require instanceof checks at runtime which may be ugly.

Hi @martinoconnor , thank you for the reivew. It helped fixing it better.

Agree, type safety would be an issue if consumer passes Map of custom objects. Updated the code to warn (throwing IllegalArugment) in that case. This change supports Map and/or Collection of objects of specified type/array type only. Restricted the checks to the minimal.

Please review the updated code when you have time.

Hello,

Adding this feature would allow me to migrate from JWT 2 to JWT 3 as one of the claims we use is a Map and that cannot be changed. Is anything pending here?

Hello,

Adding this feature would allow me to migrate from JWT 2 to JWT 3 as one of the claims we use is a Map and that cannot be changed. Is anything pending here?

Hi @ornom0n ,

I'm waiting on review, once the review is done, we are good to merge.
If it is helpful to you, please go ahead with the use. And please have a look at checks once, though major are passed.

Any hope for getting this reviewed and also please check, #297 as well.