@drennalls Can you please try the latest stable version (2.3.0), which has the Go API client refactored?

This happens in version 2.4.0-SNAPSHOT. Reproduced as follows:

Got petstore.yaml

And add:

...
      vaccinated:
        type: boolean
        description: indicate if pet is vaccinated
...

To the Pet object definition.

Generate the client:

$ ./run-in-docker.sh generate -i issue7391.yaml -l go -o /gen/out/issue7391 -DpackageName=issue7391
$ ln -s ${PWD}/out $(go env GOPATH)/src/out

Create a dummy server:

from flask import Flask, request

app = Flask(__name__)

@app.route('/pet', methods=['POST'])
def root():
    content = request.json
    print content
    return "all right"

app.run(port=8080)

Run a Go test:

package main

import (
	"fmt"
	"out/issue7391"
	"testing"
)

func TestPost(t *testing.T) {
	config := issue7391.NewConfiguration()
	config.BasePath = "http://localhost:8080"
	client := issue7391.NewAPIClient(config)

	pet := issue7391.Pet{
		Name: "john",
		// Vaccinated: false,
	}

	res, err := client.PetApi.AddPet(nil, pet)
	fmt.Printf("%+v\n%+v\n", res, err)
}

Running with or without commenting on that line, the server logs:

{u'name': u'john', u'photoUrls': None}
127.0.0.1 - - [31/Jan/2018 11:59:48] "POST /pet HTTP/1.1" 200 -

Manually changing the model_pet.go generated from:

...
	Vaccinated bool `json:"vaccinated,omitempty"`
...

to

...
	Vaccinated bool `json:"vaccinated"`
...

Again, running with or without commenting the Vaccinated: false line, the server logs:

127.0.0.1 - - [31/Jan/2018 11:59:58] "POST /pet HTTP/1.1" 200 -
{u'vaccinated': False, u'name': u'john', u'photoUrls': None}

So removing omitempty won't fix the problem, since the property will always be false if empty. Surprisingly, changing the property to:

...
	Vaccinated *bool `json:"vaccinated"`
...

Actualy works as intended. Maybe it's an option?

/cc @drennalls @wing328

I thought removing omitempty would work. Can you also share the Go version you're using?

cc @antihax @bvwells

Sure:

$ go version
go version go1.9.3 linux/amd64

@drennalls hello, setting default value should help

    vaccinated:
        type: boolean
        default:false
        description: indicate if pet is vaccinated

I seem to be running into this issue as well. Providing a default as @tenmozes suggested yields

 Vaccinated *bool `json:"vaccinated,omitempty"`

which does work. However, my question is whether we should also consider using this style even when a default is NOT provided?

Personally, I can't think of an instance where the existing

 Vaccinated bool `json:"vaccinated,omitempty"`

would be preferred over the pointer version that is generated when you provide a default. What do y'all think / can you think of one such scenario? In fact, wouldn't we run into this same issue with all scalar types (e.g., int, string)? Under the current scheme there is no way to pass 0 or an empty string unless you specify a default.

It seems the fix by setting a default outlined in #7391 (comment) does not work for fields of type number when the default is 0.

No default

The following:

    latitude:
        type: number
        description: the latitude in decimal format

leads to

Latitude float32 `json:"latitude,omitempty"` 

as expected.

Default != 0

Setting a default other than 0 will lead to the expecting pointer construct, such as:

    latitude:
        type: number
        default: 5
        description: the latitude in decimal format

leads to

Latitude *float32 `json:"latitude,omitempty"` 

as expected after knowing this fixes it for bool fields as well.

Default == 0

However, when the default is 0 (which is the default value of a float32, similar to how false is the default value of a bool), we don't end up with the pointer construct:

    latitude:
        type: number
        default: 0
        description: the latitude in decimal format

leads to

Latitude float32 `json:"latitude,omitempty"` 

So, fixing this by setting a default, does not work if the default is 0.

I'm testing with version CLI 2.4.8 and it's no longer generating pointers for booleans when setting a default value.

I am also seeing the bool issue - on Golang 1.12.6 and go-swagger latest (c49ea4ca2).

The fix does seem to be making the struct member a pointer in the model - which as suggested, a default value does - and also making the property required, eg :

  GroupQueryResult:
    description: Result of a group query
    type: object
    required:
      - group
      - user
      - isMember
    properties:
      user:
        type: string
      group:
        type: string
      isMember:
        type: boolean

any updates?

Any updates?
It's a real problem when you are dealing with a complex and huge swagger api.

@vvalchev Can you help please?

I tried but couldn't figure it out. Can you help me make boolean type not omitempty and be always a pointer type.

@wkgcass Or anyone out there for solutions,

I used -t (template directory) while generating for golang. And under model.mustache, I specified

{{#description}} // {{{description}}} {{/description}} {{name}} {{^isEnum}}{{^isPrimitiveType}}{{^isContainer}}{{^isDateTime}}*{{/isDateTime}}{{/isContainer}}{{/isPrimitiveType}}{{/isEnum}}{{#isBoolean}}*{{/isBoolean}}{{{datatype}}} `json:"{{baseName}}{{^required}},omitempty{{/required}}"{{#withXml}} xml:"{{baseName}}"{{/withXml}}` {{/vars}} {{/isComposedModel}} }{{/isEnum}}{{/model}}{{/models}}

Notice {{#isBoolean}}*{{/isBoolean}}