anyway it’s a good point and I want to learn more about the specific implications of each approach
it’s a huge lib
if I would have known how much work it was going to be I would probably never have started
any idea what might be causing this?
sorry that should be
restapi/operations/NAME_api.go the file is just missing
ah nailed down the operation
Commenting this out from the spec fixes it:
'/_debug':
get:
tags: ['_debug']
operationId: 'getDebug'
summary: 'Debug route strictly for testing.'
responses:
'200':
description: 'Debug result.'
schema: { type: 'any' }
it’s not supported by the swagger spec
it’s valid json schema but the swagger people chose to not allow it
@chakrit but allOf should be very much supported
i have tons of tests on that
anyOf is not supported for codegen at this moment though
as discussed in #41
with respect to inheritance and polymorphism: how does the generated server code represent models composed with discriminators and allOf?
I tried generating a server using the models from the Models with Polymorphism Support example, which uses Pet as a parent interface for Cat and Dog. Both Cat and Dog contain properties inherited from Pet, as well as their own unique properties. The models for Cat and Dog seem to be empty structs (
type Cat struct {}). Is that expected?
Apologies if that is a noob question.
thanks for letting me know :)
go-swagger/go-swagger#65
If I'm understanding the swagger spec correctly, a path supporting a schema with a discriminator would support operations using any schema which inherits the top-level schema.
So, in the example above, a POST to /pets that accepts schema of type Pet would also accept a post matching a Cat schema like { "petType": "Cat", "name":"Meow", "huntingSkill": "lazy" }
i’ll be back in 10 minutes, quick meeting here at work
From a Go programmatic perspective, I would imagine that a handling function for a path like that would need to use an interface. Something like:
type iPet interface {}
type Pet struct { petName, name string }
type Cat struct { Pet, huntingLevel string }
type Dog struct { Pet, packSize int }
type AddPetParams struct {
// Pet to add to the store
Pet iPet
}
func (fn AddPetHandlerFunc) Handle(params AddPetParams) (*iPet, error) {
return fn(params)
}
// Actual handler
func addPet(params AddPetParams) (*iPet, error) {
switch params.Pet.(type) {
case Cat:
// handle cat
case Dog:
// handle Dog
case Pet:
// handle untyped Pet
default:
return nil, fmt.Errorf("not a known pet; this should be captured by validation?")
}
}
you don’t strictly require the iPet thing but yes I think you’re on the right track there
and the code generator needs to do this as deser/ser time
I have very little experience in this space, but let me know if I can help!
@/all I’m moving this to slack, I’m getting more time to spend on this project in the next few weeks, and I want to reduce the amount of chat clients I have to deal with. You can join the slack room here: https://slackin.goswagger.io/
@casualjim a dedicated slack for one project is a bit obscene I would suggest if you want people to join just make a channel on the primary GO slack http://blog.gopheracademy.com/gophers-slack-community/
created a #go-swagger channel there
I can’t add integrations then like circle ci notifications
Sorry for a silly question, but I'm just getting started with the examples and I'm trying to add a method to a URL, but I get the
Schema error at paths['/example'].put
should be object error and I can not seem to figure out what I'm doing wrong.paths:
/example:
# In this operation we do not apply the security, because it was applied globally above.
# The security will be applied to this operation for that reason.
get:
summary: Server example operation
description: This is an example opeartion to show how security is applied to the call.
responses:
200:
description: OK
put:
responses:
200:
description: My cool new method
Hi folks, just joined gitter and this channel. I have been working on a terraform plugin that configures itself at runtime based on an OpenAPI 2.0 spec and figured it might be of interest to some of the audience here...I was wondering if it'd be fine to share the repo link here, wasn't sure about the channel policies so wanted to ask first :)