boolean type no longer generated on properties after 2.0

[Jakob-Espersen]

I am having a problem with the types generated for my properties after upgrading from laravel 10 to 11.

previous output would look something like this

"boolean_property": {
    "type": "boolean",
    "description": "boolean",
    "default": "0",
    "nullable": false,
    "example": false
},

now this is generated:

"boolean_property": {
    "type": "integer"
},

[Mezatsong]

hm.. ok ok, but what is your main concern please ?

[Mezatsong]

I performed this upgrade to improve the conformance to the Open API Specification (OpenSpec) standards.

[Jakob-Espersen]

hm.. ok ok, but what is your main concern please ?

Hello, Thank you for the responses!

Ok i see. My concern is that i like to use my swagger spec to generate types for my frontend code (typescript) + i usually cast my database values to booleans.
And with new generated spec, i can't see how that is possible for me to generate boolean types.
I Don't know much about the OpenSpec standarts but would an output like -

"boolean_property": {
    "type": "boolean"
},

not be conformative?

[Jakob-Espersen]

Hi again @Mezatsong 


I believe i found the root of the issue to be the cleanDatabaseType method. 

Since the column type of boolean in my case is returned as tinyint(1) and thus will be transformed to tinyint.

I have made a pull request with a suggestion fix for this.

#25