Francois LASNE
Francois LASNE
arfter reading carrefully the specification around Oauth 2.1 vs Oauth2 , 2.1 is mostly precision in the protocole , good practices , and depreciation of unsecured model . but till...
after reflexion it gives me to point : swaggerUI did it ... because there is a need for sure , it is important to know if the Identity provider support...
@webron should this ticket beeing closed ? to me Odata has followed it s own pattern / way that would be quite difficult to map in OAS , especially all...
not sure that this should goes to OAS spec, as the OAS spec does not dictate any model of resource , pattern , can be REST , can be RPC...
I would agree with @pleothaud here being the link https://www.rfc-editor.org/rfc/rfc6749#section-3.2 this may deserve to set this field as deprecated in 3.2 version , and to remove it for OAS 4.0...
@chohmann tested with Dog as a property of another Object the bug looks not there ! see below spec - /dogSingle + { "name" = "happy" } => no issue...
thanks @chohmann , it could be a feature ... or a tiny comment in the documentation would also make the deal
May be add as well a filter on the reporting HTML file i am still not clear on what this kind of output means Test Name: BOPLA Test Test Result:...
what was the version of the OAS spec ? because in recent version nullable : true is not supported , null beeing a definitive type so sould be type :...
should a ticket been raised ?