how to return an existing type plus additional cookies ? about goa

[raphael]

This seems to be a bug in the OpenAPI generation, the newInstance operation should use the type Instance and not InstanceWithCookies.

[zig]

Thanks for the fix and explanations :)

[zig]

I also notice that returned (set) cookies are not documented in the openapi.

Maybe what we would need in this case, instead of defining (extend) a new type with cookies, which is a bit weird (and define a new type name), would be to be able to define Result as the combination of several things, in this case it would be 'Instance' + the cookie. It would kind of merge all these in an anonymous type.

But right now if I try to do this :

	Method("newInstance2", func() {
		Result(Instance, func() {
			Attribute("cookie", String)
		})
		HTTP(func() {
			POST("/instance2")
			Response(StatusOK, func() {
				Cookie("cookie")
				CookieMaxAge(3600 * 24 * 365)
				CookieSecure()
				CookieHTTPOnly()
				CookiePath("/")
			})
		})
	})

I get this error : [design/test.go:45] can't define child attribute "cookie" on attribute of type Instance *expr.UserTypeExpr in attribute

[raphael]

Yeah the above isn't valid DSL. Extend should work and would be the proper way to do what you want. For now though you could use your own function that defines the same attributes in two different types and add an additional cookie attribute to the InstanceWithCookies type.

[zig]

The example I provided also has in comment the method you suggest where I use a function instead of Extend, but this leads to the same bug, where only InstanceWithCookies is defined in the openapi.

[raphael]

Thanks for the repro, this is fixed in #3379, a few things to note though:

1. The fact that only one type is being generated is correct and by design. That is because the shape of the response bodies for both API endpoints are actually the exact same and Goa ensures that it won't create arbitrary schemas for types that are structurally identical. Meta("openapi:typename") can be used to override the name generated in the OpenAPI specification (Goa will use the name of the first type from which the body is derived by default).
2. The OpenAPI specification does not define a discrete attribute for cookies in responses (it does for cookies in requests). Instead official examples add the "Set-Coookie" header so this is what the PR linked above does.