fix: add flag to force object

[bshaffer]

see #413

[mfn]

Is it possible to add a test for this?

[bshaffer]

@mfn sure can! done. Thanks for not letting me be lazy :)

[pazzernick]

I tested it in the field... the change broke existing code that wasn't expecting the payload to be converted to object form! e.g. my final JWT payload should contain some Arrays, and is no use when entirely object form.

My workaround/fix is to comment out this recent change...

Can JSON_FORCE_OBJECT be 'added' only when asked for, perhaps via a global property and method-chaining.

Given that 'json_encode' will create JSON objects, if PHP objects are supplied... I would default to the original code, and only add the JSON_FORCE_OBJECT when explicitly enabled via the new method.

[bshaffer]

I did not consider this edge case.... the problem we were trying to solve was to ensure that an array type (or other types such as int) were not returned from JWT::decode. However, you're right, I think we need to revert this change and go about it a different way...

[bshaffer]

@pazzernick this is now fixed in v6.1.2. Thank you for pointing this out!