How to restore enum's schema reference?

[apasquini95]

Hi everybody, I recently updated scramble from version 0.13.4 to 0.13.10 and I noticed that now enum schemas are always inline. Is there a way to make again the schema as a reference?

Desired:

"MyRequest": {
    "type": "object",
    "properties": {
        "myEnumValue": {
            "$ref": "#/components/schemas/MyEnum"
        }
    },
    "required": [
        "myEnumValue"
    ],
    "title": "MyRequest"
},
"MyEnum": {
    "type": "integer",
    "enum": [
        1,
        2,
        3,
        4,
        5
    ],
    "title": "MyEnum"
}

Actual:

"MyRequest": {
    "type": "object",
    "properties": {
        "myEnumValue": {
            "type": "string",  // Why string and not integer as before?
            "enum": [
                "1",
                "2",
                "3",
                "4",
                "5"
            ]
        }
    },
    "required": [
        "myEnumValue"
    ],
    "title": "MyRequest"
}

Can someone please help me?

[romalytvynenko]

Hey @apasquini95
Can you show me the real code example so I can reproduce?

[apasquini95]

I created a branch on this public repository.
https://github.com/apasquini95/demo_scramble/tree/enum_schema_inline

The request has a param which is validated against the Illuminate\Validation\Rule::enum method. Before the update, scramble could produce a schema reference for the enum schema, while now it is always inline and string. Am I missing something?

[apasquini95]

I tried to figure out the problem and it seems to be not directly related to scramble 0.13.10. Upgrading my composer packages, also Laravel has been updated from version 12.38.1 to 12.48.1: with scramble at version 0.13.10 and laravel/framework at version 12.38.1 the enum schema is still by reference and not inline. The problem comes with laravel 12.48.0: I tried all versions between 12.38.1 and 12.47.0 and the openapi specification is still correct. Maybe the framework has changed/missed something in the latest version and scramble has not been yet adapted?

[apasquini95]

Version 1.13.11 has resolved the issue
https://github.com/dedoc/scramble/releases/tag/v0.13.11