feat: Support x-go-name property extension

[emilekm]

This implements a feature requested in #468.

The extension name x-go-name comes from go-swagger.

Example schema:

components:
  schemas:
    Person:
      type: object
      properties:
        id:
          type: string
          x-go-name: ID
        pet_id:
          type: string
          x-go-name: PetID

Output:

type Person struct {
	ID string `json:"id"`
	PetID string `json:"pet_id"`
}

[octomad]

Excellent. Exactly what was needed.

[octomad]

Just checking in. Will this be merged soon?

[Penthious]

Also checking when this will be merged in.

[Jacob-Roberts]

This has broken the generated code. The types file that is created will correctly respect this. But the client that is generated will use the non-x-go-name version

[emilekm]

This has broken the generated code. The types file that is created will correctly respect this. But the client that is generated will use the non-x-go-name version

Could you provide a sample of the code that is broken? I don't think it's broken and you are referring to URL parameters (since query params work fine).

E: the referenced MR isn't passing the tests, but it should fix your particular problem (if I am correct in my assesment)

[emilekm]

I'm currently on vacation, but when I get back I'll try to fix this (unless it's already being worked on). Good catch

…

On Thu, 5 May 2022, 20:50 Jacob Roberts, ***@***.***> wrote: This has broken the generated code. The types file that is created will correctly respect this. But the client that is generated will use the non-x-go-name version — Reply to this email directly, view it on GitHub <#517 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJTNLQT4K3XPD7W7KO62YLVIQKAHANCNFSM5NTBUJJA> . You are receiving this because you authored the thread.Message ID: ***@***.***>