What
Our OpenAPI arguments are mapped (as a whole) to a Views exposed filter/argument/pager.
I have the need of allowing, when dealing with multiple allowed values (e.g all valid OAI verbs) to define , if verb== ListSets -> Map to View X, Argument Y, but if verb==ListRecord Map to View Z, Argument Gamma. Since Mapping is already out of the OpenAPI specs, I can allow the current behavior or a new one, requires a different way of saving the Configs/reading them back in the controller (and it needs to be "current way" aware so people don't have to change their configs/me write an Update hook)
Now. For the UUID validator. I would love to have a custom "type" (UUID with prefix/suffix/separator) that allows an argument to be passed as
identifier="oai:domain:uuid" with prefix settings in the OpenAPI (oai:domain:), suffix settings *(if any) and a separator (":").
Because there is no Valid native validator for this need in the OpenAPI specs I will have to
A) modify the value myself from the request before feeding the validator, OR, B) create my own custom validation class and (find how to) inject it into the OpenAPI Validator/parser class.
What
Our OpenAPI arguments are mapped (as a whole) to a Views exposed filter/argument/pager.
I have the need of allowing, when dealing with multiple allowed values (e.g all valid OAI verbs) to define , if
verb== ListSets-> Map to View X, Argument Y, but ifverb==ListRecordMap to View Z, Argument Gamma. Since Mapping is already out of the OpenAPI specs, I can allow the current behavior or a new one, requires a different way of saving the Configs/reading them back in the controller (and it needs to be "current way" aware so people don't have to change their configs/me write an Update hook)Now. For the UUID validator. I would love to have a custom "type" (UUID with prefix/suffix/separator) that allows an argument to be passed as
identifier="oai:domain:uuid"with prefix settings in the OpenAPI (oai:domain:), suffix settings *(if any) and a separator (":").Because there is no Valid native validator for this need in the OpenAPI specs I will have to
A) modify the value myself from the request before feeding the validator, OR, B) create my own custom validation class and (find how to) inject it into the OpenAPI Validator/parser class.