Field with Option Set value not showing up in swagger

Need help APIs
1

I have an object of type Submitted Application. One of its fields is Current Status, which is of type Application Status, which is an Option Set. When I poke the swagger endpoint, the Current Status field isn’t showing up in the definition, which presumably means it can’t be updated through the API, which is a substantial piece of the desired functionality. Are Option Set values not supported in the API? Am I missing something?

Screen Shot 2020-11-01 at 5.31.29 PM
Screen Shot 2020-11-01 at 5.31.29 PM1574×982 75.6 KB

"definitions": {
    "submittedapplication": {
        "type": "object",
        "properties": {
            "original_application_custom_application": {
                "type": "string",
                "description": "'Original Application ID' field of the current Submitted Application ('application' represented by a unique ID)"
            },
            "policy_documents_list_file": {
                "type": "array",
                "description": "'Policy Documents' field of the current Submitted Application",
                "items": {
                    "type": "string"
                }
            },
            "policy_id_text": {
                "type": "string",
                "description": "'Insurer Policy ID' field of the current Submitted Application"
            },
            "Created Date": {
                "type": "string",
                "format": "date",
                "description": "'Created Date' field of the current Submitted Application"
            },
            "Modified Date": {
                "type": "string",
                "format": "date",
                "description": "'Modified Date' field of the current Submitted Application"
            },
            "Created By": {
                "type": "string",
                "description": "'Created By' field of the current Submitted Application ('user' represented by a unique ID)"
            },
            "_id": {
                "type": "string",
                "description": "'unique ID' field of the current Submitted Application"
            },
            "Slug": {
                "type": "string",
                "description": "'Slug' field of the current Submitted Application"
            }
        }
    },
    "submittedapplicationBody": {
        "type": "object",
        "properties": {
            "original_application_custom_application": {
                "type": "string",
                "description": "'Original Application ID' field of the current Submitted Application ('application' represented by a unique ID)"
            },
            "policy_documents_list_file": {
                "type": "array",
                "description": "'Policy Documents' field of the current Submitted Application",
                "items": {
                    "type": "string"
                }
            },
            "policy_id_text": {
                "type": "string",
                "description": "'Insurer Policy ID' field of the current Submitted Application"
            }
        }
    }
},
2

I have the same issue :cry:

3

Looks like it’s fixed!

4

Now the JSON schema of the definitions is invalid as Bubble introduced a new type “option set” which is not valid, but you know, one can’t have it all :sweat_smile:

5

Indeed, ‘option set’ is not valid.

Structural error at definitions.roleBody.properties.permissions.items.type

should be equal to one of the allowed values allowedValues: array, boolean, integer, number, object, string

Jump to line 15770

They could have checked the standard before applying a fix :-/

6

Also, too bad the Notes are discarded when they could be used in the Description.

7

@emmanuel any update on a possible fix for that ?
There is a standard for a reason.