On 2020-02-22 10:59, Chen Xinyan wrote:
> Just out of curiosity, is there any recommended way to parse out "which" parameter goes wrong. For example, we have "unknown_action" before. Now it gets merged into "badvalue", and the response looks like this:
>
> ...
>
> Do I have to parse into .error.info content to know the parameter name?

For a long-term solution, I'd recommend filing a task to make the API
return this data in another way.

As I said in the original announcement, "If you have a use case where knowing which parameter triggered the error is needed, please let us know (by replying to this message or by filing a request in Phabricator) and we'll add the necessary error metadata."

What's the use case, other than just curiosity?