summaryrefslogtreecommitdiffstats
path: root/lib/public/Activity
diff options
context:
space:
mode:
authorJoas Schilling <coding@schilljs.com>2019-01-25 12:12:59 +0100
committerJoas Schilling <coding@schilljs.com>2019-01-25 12:12:59 +0100
commit47f63da07cb8fd9edd0cc2751029d14ed39072e6 (patch)
treea8d622a54c260e1d71de624c0c84f3a13d9ab8d6 /lib/public/Activity
parent58799202ebb42397fd5673ac935d97ded5a1a4dc (diff)
downloadnextcloud-server-47f63da07cb8fd9edd0cc2751029d14ed39072e6.tar.gz
nextcloud-server-47f63da07cb8fd9edd0cc2751029d14ed39072e6.zip
Update documentation of setParsed* and setRich*
Signed-off-by: Joas Schilling <coding@schilljs.com>
Diffstat (limited to 'lib/public/Activity')
-rw-r--r--lib/public/Activity/IEvent.php42
1 files changed, 42 insertions, 0 deletions
diff --git a/lib/public/Activity/IEvent.php b/lib/public/Activity/IEvent.php
index aee00039b65..e380eca5c24 100644
--- a/lib/public/Activity/IEvent.php
+++ b/lib/public/Activity/IEvent.php
@@ -100,6 +100,17 @@ interface IEvent {
public function setSubject(string $subject, array $parameters = []): self;
/**
+ * Set a parsed subject
+ *
+ * HTML is not allowed in the parsed subject and will be escaped
+ * automatically by the clients. You can use the RichObjectString system
+ * provided by the Nextcloud server to highlight important parameters via
+ * the setRichSubject method, but make sure, that a plain text message is
+ * always set via setParsedSubject, to support clients which can not handle
+ * rich strings.
+ *
+ * See https://github.com/nextcloud/server/issues/1706 for more information.
+ *
* @param string $subject
* @return $this
* @throws \InvalidArgumentException if the subject is invalid
@@ -114,6 +125,16 @@ interface IEvent {
public function getParsedSubject(): string;
/**
+ * Set a RichObjectString subject
+ *
+ * HTML is not allowed in the rich subject and will be escaped automatically
+ * by the clients, but you can use the RichObjectString system provided by
+ * the Nextcloud server to highlight important parameters.
+ * Also make sure, that a plain text subject is always set via
+ * setParsedSubject, to support clients which can not handle rich strings.
+ *
+ * See https://github.com/nextcloud/server/issues/1706 for more information.
+ *
* @param string $subject
* @param array $parameters
* @return $this
@@ -146,6 +167,17 @@ interface IEvent {
public function setMessage(string $message, array $parameters = []): self;
/**
+ * Set a parsed message
+ *
+ * HTML is not allowed in the parsed message and will be escaped
+ * automatically by the clients. You can use the RichObjectString system
+ * provided by the Nextcloud server to highlight important parameters via
+ * the setRichMessage method, but make sure, that a plain text message is
+ * always set via setParsedMessage, to support clients which can not handle
+ * rich strings.
+ *
+ * See https://github.com/nextcloud/server/issues/1706 for more information.
+ *
* @param string $message
* @return $this
* @throws \InvalidArgumentException if the message is invalid
@@ -160,6 +192,16 @@ interface IEvent {
public function getParsedMessage(): string;
/**
+ * Set a RichObjectString message
+ *
+ * HTML is not allowed in the rich message and will be escaped automatically
+ * by the clients, but you can use the RichObjectString system provided by
+ * the Nextcloud server to highlight important parameters.
+ * Also make sure, that a plain text message is always set via
+ * setParsedMessage, to support clients which can not handle rich strings.
+ *
+ * See https://github.com/nextcloud/server/issues/1706 for more information.
+ *
* @param string $message
* @param array $parameters
* @return $this