success is declared as a boolean when it is a string in production and test environments.

[LucasRxTx]

Describe the bug
success has been declared as a boolean when it is actually a string. Here is one example of many:

adyen-openapi/json/Webhooks-v1.json

Line 2065 in 4d59745

"success" : {

To Reproduce
Look at other definitions of success in the openAPI documentation and see that success is a string.
Look at the example notifications in the openAPI documentation; success is a string.
Look at a production notification and see that success is a string.
Look at a testing environment notification and see that success is a string.

Expected behavior
success should be a string. It would have been great if success was actually a boolean, but at this point it has to be a string to break integrations.

Screenshots
None

Desktop (please complete the following information):
irrelevent

Smartphone (please complete the following information):
irrelevent

Additional context
This has caused issues in the past. We have getters for success that coax the value to a boolean if it is a string or a bool because it is unclear in your openAPI spec if success will always be a string, or sometimes may possibly be a bool.