Hi,

It's a concept only but we need this at @livesession.
The case is like that:

Let's say we have a core structures defined schema.yaml in our core golang package and want to reuse that so we have to:

generate ./schema.yaml inside our core package
then in our api we need to import that schemas to our openapi and based on that schema generate a golang server too
We would like to have references to core instead of a new objects. Plus we want to have schema.gen.go inside core package.

Why it's needed? Because x-go-type overwrite what type is generated so using this method inside core package we would get types that does not exists. If we use that from api perspective (which use core it's fine cuz the references are already generated)