Re: Swagger does not like included JSON Schema object because of "$schema" and "id" properties

Please check out the specification to see what subset of JSON schema is supported: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md The spec does not support the JSON schema draft 4 100%. > On Ju

Swagger does not like included JSON Schema object because of "$schema" and "id" properties

>From my understanding of JSON Schema, a schema document can (and should) include a parameter for the version of its schema and an id that uniquely identifies the definition, e.g. { "$schema": "http://json-schema.org/draft-04/schema#";, "id": "mydef", "type": "object", "title": "

Re: Noob struggling to define a route...

Thank you! That did it! -- Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Leaf Group. Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited a

Re: Noob struggling to define a route...

You should change this: /x: /y: to this: /x/y: Note the path segment (/a, /x/y, etc) must be a single unique string. > On Jun 14, 2017, at 11:25 AM, 'Toe Dipper' via Swagger > wrote: > > I'm evaluating swagger and I'm having trouble defining a simple route in my > app. It's something li

Noob struggling to define a route...

I'm evaluating swagger and I'm having trouble defining a simple route in my app. It's something like "/x/y" where there requesting "/x" by itself is not considered a valid route. I've been trying the online swagger editor, but I can't figure out how to resolve the error: Schema error at path

Re: Better date/time types?

JSON Schema does allow for a "date-time" string format, but it's not a very common one (even though its an RFC standard), e.g. sample JSON Schema definition: { "type": "string", "format": "date-time" } See https://spacetelescope.github.io/understanding-json-schema/reference/string.htm

Re: POST Endpoint - How to give sample JSON body

A schema isn't the same as an example body (although you could use the JSON schema's "default" property to include an example body). I think the OP wanted to know how to include a full sample body, e.g. http://swagger.io/docs/specification/adding-examples/ -- Please NOTE: This electronic mess

apiclient.java is always ignoring the code added in apiclient.mustache file

Hi, I tried to add some content into apiclient.mustache file. but the apiclient.java is always ignoring the changes and the code change is not reflected. Thanks, Naveen -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this grou

Re: OpenAPI Specification (FKA Swagger Spec 3.0) is under development

https://teespring.com/coolpuppy -- 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 swagger-swaggersocket+unsubscr...@googlegroups.com. For more options, visit https://gr

Re: OpenAPI Specification (FKA Swagger Spec 3.0) is under development

https://teespring.com/coolpuppy -- 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 swagger-swaggersocket+unsubscr...@googlegroups.com. For more options, visit https://gr

Re: How to define a set of standard parameters for each path item

On Wed, 6/14/17, 'Philipp' via Swagger wrote: Subject: Re: How to define a set of standard parameters for each path item To: "Swagger" Date: Wednesday, June 14, 2017, 11:38 AM Hey, thanks for your last example. I found my mistake. A copy

Re: How to define a set of standard parameters for each path item

Hey, thanks for your last example. I found my mistake. A copy from my first post, second example: parameters: sessionInformation: - name: sessionInformation in: body required: true schema: $ref: '#/definitions/Session' I placed a '-' before the name, that causes