Remove redundant 'Required' annotations from event fields

pull/977/head
Richard van der Hoff 7 years ago
parent 51e248a1db
commit e5e249dce1

@ -3,11 +3,12 @@ properties:
content: content:
description: The fields in this object will vary depending on the type of event. description: The fields in this object will vary depending on the type of event.
When interacting with the REST API, this is the HTTP body. When interacting with the REST API, this is the HTTP body.
title: EventContent
type: object type: object
type: type:
description: The type of event. This SHOULD be namespaced similar to Java package description: The type of event. This SHOULD be namespaced similar to Java package
naming conventions e.g. 'com.example.subdomain.event.type' naming conventions e.g. 'com.example.subdomain.event.type'
type: string type: string
required:
- type
title: Event title: Event
type: object type: object

@ -4,17 +4,17 @@ description: In addition to the Event fields, Room Events have the following add
fields. fields.
properties: properties:
event_id: event_id:
description: Required. The globally unique event identifier. description: The globally unique event identifier.
type: string type: string
room_id: room_id:
description: Required. The ID of the room associated with this event. description: The ID of the room associated with this event.
type: string type: string
sender: sender:
description: Required. Contains the fully-qualified ID of the user who *sent* description: Contains the fully-qualified ID of the user who *sent*
this event. this event.
type: string type: string
origin_server_ts: origin_server_ts:
description: Required. Timestamp in milliseconds on originating homeserver description: Timestamp in milliseconds on originating homeserver
when this event was sent. when this event was sent.
type: number type: number
unsigned: unsigned:

Loading…
Cancel
Save