Everything gets rendered as string in the response

[softzer0]

#3908 - this fix ensures that every type of variable in the exception response is rendered as a string value in JSON. I know that there's a workaround for avoiding that but it's rather "non-robust" (because it requires overriding init), and I just think it's strange to enforce string for all fields without any specific reason. Therefore, can that function be made in more conventional way, e.g. to skip conversion of numbers to strings?

[xordoquy]

Closing this it as it isn't actionnable and too vague. Note that this only applies to exceptions.
Will consider a PR with test case though.

[tomchristie]

We could consider this, but I can't understand the issue from this description.

every type of variable in the exception response is rendered as a string value in JSON

Can you give an example? When wouldn't you want a string value in an error detail?

[softzer0]

@tomchristie: For example, when returning an error number and then using the comparison operator ===. It would fail on that part.

[tomchristie]

Implement a custom exception handler if you want to be able to return integers as error messages.
Personally I can't see either a good use case for it, or a way of doing that, that'd be consistent with the kind error messages we return.