Update doc to remove call to setParsedSubject

docs/notification-workflow.md

@@ -82,7 +82,7 @@ class Notifier implements \OCP\Notification\INotifier {
 	}
 
 	/**
-	 * Human readable name describing the notifier
+	 * Human-readable name describing the notifier
 	 * @return string
 	 */
 	public function getName(): string {
@@ -154,9 +154,15 @@ class Notifier implements \OCP\Notification\INotifier {
 		}
 	}
 
-	// This is a little helper function which automatically sets the simple parsed subject
-	// based on the rich subject you set.
-	protected function setParsedSubjectFromRichSubject(INotification $notification) {
+	/**
+	 * This is a little helper function which automatically sets the simple parsed subject
+	 * based on the rich subject you set. This is also the default behaviour of the API
+	 * since Nextcloud 26, but in case you would like to return simpler or other strings,
+	 * this function allows you to take over.
+	 *
+	 * @param INotification $notification
+	 */
+	protected function setParsedSubjectFromRichSubject(INotification $notification): void {
 		$placeholders = $replacements = [];
 		foreach ($notification->getRichSubjectParameters() as $placeholder => $parameter) {
 			$placeholders[] = '{' . $placeholder . '}';

docs/ocs-endpoint-v2.md

@@ -176,4 +176,4 @@ In order to check whether a set of notification ids (max. 200 items per request)
 a client can send a POST request against `/ocs/v2.php/apps/notifications/api/v2/notifications/exists` with
 the integer list provided as `ids` field on the POST body.
 
-**Note:** This endpoint was added for Nextcloud 27, so check for the `exists` capability first.
+**Note:** This endpoint was added for Nextcloud 27 and 26.0.1, so check for the `exists` capability first.