From 3b6fd5c17d454967faa4546c90c84ae58fae80e1 Mon Sep 17 00:00:00 2001 From: Alexandru Ungureanu Date: Sat, 12 Sep 2020 22:19:13 +0300 Subject: [PATCH 1/2] Corrected unintended text emphasis Signed-off-by: Alexandru Ungureanu --- developer_manual/client_apis/OCS/ocs-api-overview.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/developer_manual/client_apis/OCS/ocs-api-overview.rst b/developer_manual/client_apis/OCS/ocs-api-overview.rst index 3b39138b1..49b864cf7 100644 --- a/developer_manual/client_apis/OCS/ocs-api-overview.rst +++ b/developer_manual/client_apis/OCS/ocs-api-overview.rst @@ -212,9 +212,9 @@ An example curl command would be: curl -i -u master -X GET -H "OCS-APIRequest: true" 'https://my.nextcloud/ocs/v2.php/core/autocomplete/get?search=JOANNE%40EMAIL.ISP&itemType=%20&itemId=%20&shareTypes[]=8&limit=2' -That would look for JOANNE@EMAIL.ISP as guest user. Maximum 2 results to be returned - for a regular user, the shareTypes array would carry only "0" -. itemType and itemId are left (set to a white space), essentially they are to give context about the use case, so sorters can do their work (like who commented last). It can be an option for filtering on a later stage but you can also leave them out: +That would look for JOANNE@EMAIL.ISP as guest user. Maximum 2 results to be returned for a regular user, the shareTypes array would carry only "0". +`itemType` and itemId are left (set to a white space), essentially they are to give context about the use case, so sorters can do their work (like who +commented last). It can be an option for filtering on a later stage but you can also leave them out as per the below example. .. code:: From 04e37fc33b8ab08716273b964d461f5e54805521 Mon Sep 17 00:00:00 2001 From: Morris Jobke Date: Mon, 14 Sep 2020 16:30:19 +0200 Subject: [PATCH 2/2] Update developer_manual/client_apis/OCS/ocs-api-overview.rst --- developer_manual/client_apis/OCS/ocs-api-overview.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer_manual/client_apis/OCS/ocs-api-overview.rst b/developer_manual/client_apis/OCS/ocs-api-overview.rst index 49b864cf7..010034720 100644 --- a/developer_manual/client_apis/OCS/ocs-api-overview.rst +++ b/developer_manual/client_apis/OCS/ocs-api-overview.rst @@ -213,7 +213,7 @@ An example curl command would be: curl -i -u master -X GET -H "OCS-APIRequest: true" 'https://my.nextcloud/ocs/v2.php/core/autocomplete/get?search=JOANNE%40EMAIL.ISP&itemType=%20&itemId=%20&shareTypes[]=8&limit=2' That would look for JOANNE@EMAIL.ISP as guest user. Maximum 2 results to be returned for a regular user, the shareTypes array would carry only "0". -`itemType` and itemId are left (set to a white space), essentially they are to give context about the use case, so sorters can do their work (like who +``itemType`` and ``itemId`` are left (set to a white space), essentially they are to give context about the use case, so sorters can do their work (like who commented last). It can be an option for filtering on a later stage but you can also leave them out as per the below example. .. code::