Why catch only one type of exception ?

[qpautrat]

@AlexDpy Can you tell me why you decided to catch only this type of exception ?

Thank you mate !

[AlexDpy]

As we can see here all those exceptions extend the \UnexpectedValueException so there are all catched

[qpautrat]

As far as i know InvalidArgumentException does not extend from UnexpectedValueException.
Moreover you should let client decide if it wants to know what really happened.

[AlexDpy]

The InvalidArgumentException here is thrown when there is an error in the code.

The UnexpectedValueException is thrown when there's an error due to an external source (i.e. an expired jwt).

More infos about firebase-jwt exception in this PR

The JWTDecodeUnexpectedValueException is just here to wrap the UnexpectedValueException, and only this kind of exception. It helps to easily catch an 'external error'. Maybe it's useless and maybe we should let the raw UnexpectedValueException being thrown.

Maybe you can expose your use case so we can better understand your need ?

[qpautrat]

Fortunately I don't need, in my use case, to know what really happened. But, perhaps, later I'll.
Client should be able to know if token has expired or if signature is invalid IMO.