matrix-spec-proposals/event-schemas/schema/m.room.message$m.notice

---
allOf:
  - $ref: core-event-schema/room_event.yaml
description: 'The ``m.notice`` type is primarily intended for responses from automated clients. An ``m.notice`` message must be treated the same way as a regular ``m.text`` message with two exceptions. Firstly, clients should present ``m.notice`` messages to users in a distinct manner, and secondly, ``m.notice`` messages must never be automatically responded to. This helps to prevent infinite-loop situations where two automated clients continuously exchange messages.'
properties:
  content:
    properties:
      body:
        description: The notice text to send.
        type: string
      msgtype:
        enum:
          - m.notice
        type: string
      format:
        description: |-
          The format used in the ``formatted_body``. Currently only
          ``org.matrix.custom.html`` is supported.
        type: string
      formatted_body:
        description: |-
          The formatted version of the ``body``. This is required if ``format``
          is specified.
        type: string
    required:
      - msgtype
      - body
    type: object
  type:
    enum:
      - m.room.message
    type: string
title: NoticeMessage
type: object
Convert event schemas to yaml We've decided to make the event schemas YAML, so we might as well take advantage of it. (This conversion was done mostly automatically, except for: - s/null/"null"/ in m.room.member - reformat description in m.room.power_levels 8 years ago			`---`
			`allOf:`
			`- $ref: core-event-schema/room_event.yaml`
Make m.notice description use stricter language Signed-off-by: Johannes Löthberg <johannes@kyriasis.com> 8 years ago			description: 'The ``m.notice`` type is primarily intended for responses from automated clients. An ``m.notice`` message must be treated the same way as a regular ``m.text`` message with two exceptions. Firstly, clients should present ``m.notice`` messages to users in a distinct manner, and secondly, ``m.notice`` messages must never be automatically responded to. This helps to prevent infinite-loop situations where two automated clients continuously exchange messages.'
Convert event schemas to yaml We've decided to make the event schemas YAML, so we might as well take advantage of it. (This conversion was done mostly automatically, except for: - s/null/"null"/ in m.room.member - reformat description in m.room.power_levels 8 years ago			`properties:`
			`content:`
			`properties:`
			`body:`
			`description: The notice text to send.`
			`type: string`
			`msgtype:`
			`enum:`
			`- m.notice`
			`type: string`
Add missing format fields to m.room.message$m.notice schema. Signed-off-by: Jimmy Cuadra <jimmy@jimmycuadra.com> 5 years ago			`format:`
			`description: \|-`
			The format used in the ``formatted_body``. Currently only
			``org.matrix.custom.html`` is supported.
			`type: string`
			`formatted_body:`
			`description: \|-`
			The formatted version of the ``body``. This is required if ``format``
			`is specified.`
			`type: string`
Convert event schemas to yaml We've decided to make the event schemas YAML, so we might as well take advantage of it. (This conversion was done mostly automatically, except for: - s/null/"null"/ in m.room.member - reformat description in m.room.power_levels 8 years ago			`required:`
			`- msgtype`
			`- body`
			`type: object`
			`type:`
			`enum:`
			`- m.room.message`
			`type: string`
			`title: NoticeMessage`
			`type: object`