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
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
when validating JSON body of resource the result of validation is one error string with concatenation of all errors using new line and dash, for example:
[Error validating JSON. Error: - Invalid type String, expected Integer for clientId
- Invalid type String, expected Integer for ownershipPercentage
- Provided value 2017010100000000 is not compliant with the format date_only provided in rfc3339 for pacStartDate
- Invalid type String, expected Float for pacTotal
- Missing required field "dealerCode"]
each validation error should yield separate RamlValidationResult and should include error path
when validating JSON body of resource the result of validation is one error string with concatenation of all errors using new line and dash, for example:
each validation error should yield separate RamlValidationResult and should include error path
Aha! Link: https://mulesoft-roadmap.aha.io/features/APIRAML-35
The text was updated successfully, but these errors were encountered: