integration_types and contexts are both documented as non-nullable with defaults, but contexts can be null

[AtoraSuunva]

Description

Under Application Command Structure, both the new integration_types and contexts fields are documented as non-nullable and with defaults.

If you create an application command that doesn't specify:

• integration_types: it will be [0] (as the documentation says: "Defaults to GUILD_INSTALL (0)")
• contexts: it will be null (despite not being marked nullable and supposedly "By default, all interaction context types included for new commands.")

Is contexts supposed to behave like integration_types and return the default instead of null? Is it expected to return null?

Edit: Seems like contexts also isn't including all interaction context types by default. Any application command with "contexts": null won't be visible/usable in DMs/Group DMs, only in guilds or DMs with the bot.

Steps to Reproduce

PUT a simple command for your app that doesn't specify integration_types or contexts:

curl -H "Authorization: Bot {token}" -X PUT -H 'Content-Type: application/json' -d '[{"name":"foo", "type": 2}]' https://discord.com/api/v10/applications/{application.id}/commands

And the response will include defaults for integration_types but null for contexts:

[
  {
    "id": "{id}",
    "application_id": "{id}",
    "version": "{id}",
    "default_member_permissions": null,
    "type": 2,
    "name": "foo",
    "description": "",
    "dm_permission": true,
    "contexts": null,
    "integration_types": [
      0
    ],
    "nsfw": false
  }
]

Expected Behavior

Either:

• contexts is documented as nullable
• or contexts is given a default value like integration_types is

Current Behavior

contexts is documented non-nullable, but the API can return null

Screenshots/Videos

Client and System Information

curl 7.81.0