Thanks a lot for the quick turnaround. > On 29. Jun 2017, at 17:50, Ron Ratovsky <[email protected]> wrote: > > It’s a known issue - > https://github.com/swagger-api/swagger-editor/issues/1343 > <https://github.com/swagger-api/swagger-editor/issues/1343>. > > > > From: <[email protected] > <mailto:[email protected]>> on behalf of ALEKSEI MOKEEV > <[email protected] <mailto:[email protected]>> > Reply-To: "[email protected] > <mailto:[email protected]>" > <[email protected] > <mailto:[email protected]>> > Date: Thursday, 29 June 2017 at 8:43 > To: "[email protected] > <mailto:[email protected]>" > <[email protected] > <mailto:[email protected]>> > Subject: Re: Use of "security" attribute in POST payloads > > Yes, exactly. Screenshot: > > <image002.png> >> On 29. Jun 2017, at 17:38, Ron Ratovsky <[email protected] >> <mailto:[email protected]>> wrote: >> >> Are you talking about swagger-editor? >> >> >> >> From: <[email protected] >> <mailto:[email protected]>> on behalf of Alexei >> <[email protected] <mailto:[email protected]>> >> Reply-To: "[email protected] >> <mailto:[email protected]>" >> <[email protected] >> <mailto:[email protected]>> >> Date: Thursday, 29 June 2017 at 2:13 >> To: Swagger <[email protected] >> <mailto:[email protected]>> >> Subject: Use of "security" attribute in POST payloads >> >> I have a simple API, that accepts JSON payload, and among attributes of the >> payload I have one with name "security". >> A sample for the POST payload schema: >> definitions: >> someSchema: >> description: My schema description >> type: object >> properties: >> propertyOne: >> type: string >> propertyTwo: >> type: string >> security: >> type: object >> properties: >> propertyOne: >> type: string >> >> >> When the API is described by Swagger 2.0, it doesn't pass the validation, as >> it somehow interprets an attribute from my payload as an API's properties >> attribute. >> >> What's wrong with having a payload attribute, named security? >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Swagger" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> >> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Swagger" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/swagger-swaggersocket/iwbjam3AV1Y/unsubscribe >> >> <https://groups.google.com/d/topic/swagger-swaggersocket/iwbjam3AV1Y/unsubscribe>. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] >> <mailto:[email protected]>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "Swagger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Swagger" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/swagger-swaggersocket/iwbjam3AV1Y/unsubscribe > > <https://groups.google.com/d/topic/swagger-swaggersocket/iwbjam3AV1Y/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > <image002.png>
-- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
