Peter Van den Bosch
Peter Van den Bosch
I couldn't find any option to configure commonly used openapi validators to fail on unknown JSON properties during request processing. One feature request was refused, saying that the schema should...
Proposal for issue type: `urn:problem-type:belgif:input-validation:unknownRequestParameter` (within badRequest problem response)
I agree to drop "request", it's redundant with "input-validation"
TODO: check if those using GCloud's APIGW can work together for implementation Agreed to standardize on 'urn:problem-type:belgif:input-validation:unknownParameter' (only in combination with in: query or in: body ; in : path...
Unknown parameters should indeed be accepted in any webhook/callback request. Webhooks/callbacks aren't documented in the guide however, and I don't yet know of any implementations following the guide using them;...
Examples: ```JSON "alternateIds": [ { "sourceConfidenceLevel": 90, "type": "belgianEnterpriseNumber", "value": 244640631, "status": "validated" } ], ``` ```JSON "criteria": [ { "name": "hasReferenceAddress", "dataSource": "cbss", "value": true }, { "name": "hasReferenceAddress",...
Similar subject on resource identifier in http://opensource.zalando.com/restful-api-guidelines/#143 : > Exception: In some situations the resource identifier is not passed as a path segment but via the authorization information, e.g. an...
In GitLab by @pvdbosch on May 29, 2018, 20:44 changed the description
In GitLab by @pvdbosch on Jun 28, 2018, 10:29 requirements: - topic: enterprises, establishment ~ KBO; linked to person - document, collections operations, incl long running tasks, pagination, non-CRUD operation...
In GitLab by @pvdbosch on Jan 22, 2019, 11:43 assigned to @wsalembi