Fields with numeric consts default value are incorrectly marked as required

[nickvergessen]

Controller

	public function createRoomV2(
		string $name,
		int $type = Room::TYPE_GROUP,
		int $readOnly = Room::READ_WRITE,
		int $listable = Room::LISTABLE_NONE,
		int $messageExpiration = 0,
		int $lobbyState = Webinary::LOBBY_NONE,
		?int $lobbyTimer = null,
		int $sipEnabled = Webinary::SIP_DISABLED,
		int $permissions = Attendee::PERMISSIONS_DEFAULT,
		int $recordingConsent = RecordingService::CONSENT_REQUIRED_NO,
		int $mentionPermissions = Room::MENTION_PERMISSIONS_EVERYONE,
		string $description = '',
		?string $password = null,
		?string $objectType = null,
		?string $objectId = null,
		?string $emoji = null,
		?string $avatarColor = null,
		array $participants = [],
	): DataResponse {

Expectation

Only name is marked as required

Actual

Also fields with consts as default are marked as required

[provokateurin]

Ignore my deleted comment, I didn't read the issue correctly.

Because we can't parse the default value, we treat it like there is no default value.
I'm not sure if we should change this, but I guess we could since we not there will at least be some default value even if we don't know which one exactly.

The better way to solve this would be to support constants (both in code and phpdoc). That would make a bunch of things easier, but might require a non trivial amount of work to implement.

[nickvergessen]

Because we can't parse the default value, we treat it like there is no default value.
I'm not sure if we should change this, but I guess we could since we not there will at least be some default value even if we don't know which one exactly.

The better way to solve this would be to support constants (both in code and phpdoc). That would make a bunch of things easier, but might require a non trivial amount of work to implement.

Exactly my train of thoughts :D

Okay, then let's see if we can temporarily add a "not-required" flag somehow, until consts work