add 'obfuscate_validation_errors' option to hide details about configured limits

[rickbijkerk]

introduce option: 'obfuscate_validation_errors' to obfuscate errors

Before:

{
  "data": {},
  "errors": [
    {
      "message": "operation has exceeded maximum tokens. found [8], max [1]"
    }
  ]
}

after:

{
  "data": {},
  "errors": [
    {
      "message": "Error(s) redacted"
    }
  ]
}

[ldebruijn]

I get wanting to obfuscate errors, seems like a logical addition.

Does it make sense to add this as a global property, or rather as a setting per rule?

[rickbijkerk]

i'd say global as from security perspective on a public api you should always enable obfuscation.
Also i dont see a usecase to split it up atm, if we really see case for it in the future we can always split it up further