You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ValidateUrlV2Response, the message field is optional. In ValidateJsonV2Response, it's required (and will be returned as an empty string by default). Is there a reason for that?
The text was updated successfully, but these errors were encountered:
No, doesn't make any sense to me. I would assume that v1 send an empty string and i tried to comply with the v1 behavior (which seems kinda stupid in retrospective).
Ok, then the question is whether to always send a message or not. If it's required, that's easier for parsing (because you don't need to validate whether the field is there or not), but at the same time it's a bit stupid to send an empty message. I don't have a strong opinion on this 🙂
In ValidateUrlV2Response, the
message
field is optional. In ValidateJsonV2Response, it's required (and will be returned as an empty string by default). Is there a reason for that?The text was updated successfully, but these errors were encountered: