Attachment 154066 Details for Bug 34387 – Bug 34387: (follow-up) Minor spelling and quoting fixes

[patch] Bug 34387: (follow-up) Minor spelling and quoting fixes

Bug-34387-follow-up-Minor-spelling-and-quoting-fix.patch (text/plain), 2.63 KB, created by Katrin Fischer on 2023-07-29 21:17:17 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Katrin Fischer

Created: 2023-07-29 21:17:17 UTC

Size: 2.63 KB

patch

obsolete

>From 71d86a7d3c53d9db1c4ce3e97ba146f2b5c848a4 Mon Sep 17 00:00:00 2001
>From: Martin Renvoize <martin.renvoize@ptfs-europe.com>
>Date: Wed, 26 Jul 2023 07:15:56 +0100
>Subject: [PATCH] Bug 34387: (follow-up) Minor spelling and quoting fixes
>
>Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
>Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
>---
> api/v1/swagger/swagger.yaml | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
>diff --git a/api/v1/swagger/swagger.yaml b/api/v1/swagger/swagger.yaml
>index c2c2a3e099..2519710961 100644
>--- a/api/v1/swagger/swagger.yaml
>+++ b/api/v1/swagger/swagger.yaml
>@@ -735,10 +735,10 @@ info:
>     We can refine that with more complex matching clauses by nesting a the clause into the
>     object; `{ "fieldname": { "clause": "value" } }`.
> 
>-    Available matching clauses include ">", "<", ">=", "<=", "-like", and "-not_like".
>+    Available matching clauses include `>`, `<`, `>=`, `<=`, `-like`, and `-not_like`.
> 
>     We can filter on multiple fields by adding them to the JSON respresentation. Adding at `HASH`
>-    level will result in an "AND" query, whilst combinding them in an `ARRAY` wilth result in an
>+    level will result in an "AND" query, whilst combinding them in an `ARRAY` will result in an
>     "OR" query: `{ "field1": "value2", "field2": "value2" }` will filter the response to only those
>     results with both field1 containing value2 AND field2 containing value2 for example.
> 
>@@ -749,15 +749,15 @@ info:
> 
>     The following request would return any patron with firstname "Henry" and lastname "Acevedo";
> 
>-    `curl -u koha:koha --request GET "http://127.0.0.1:8081/api/v1/patrons/" --data-raw "{ "surname": "Acevedo", "firstname": "Henry" }"`
>+    `curl -u koha:koha --request GET "http://127.0.0.1:8081/api/v1/patrons/" --data-raw '{ "surname": "Acevedo", "firstname": "Henry" }'`
> 
>     The following request would return any patron whose lastname begins with "Ace";
> 
>-    `curl -u koha:koha --request GET "http://127.0.0.1:8081/api/v1/patrons/" --data-raw "{ "surname": { "-like": "Ace%" }"`
>+    `curl -u koha:koha --request GET "http://127.0.0.1:8081/api/v1/patrons/" --data-raw '{ "surname": { "-like": "Ace%" }'`
> 
>     The following request would return any patron whose lastname is "Acevedo" OR "Bernardo"
> 
>-    `curl -u koha:koha --request GET "http://127.0.0.1:8081/api/v1/patrons/" --data-raw "{ "surname": [ "Acevedo", "Bernardo" ] }"`
>+    `curl -u koha:koha --request GET "http://127.0.0.1:8081/api/v1/patrons/" --data-raw '{ "surname": [ "Acevedo", "Bernardo" ] }'`
> 
>     The following request embeds the related patron extended attributes data and filters on it.
> 
>-- 
>2.30.2

Actions: View | Diff | Splinter Review

Attachments on bug 34387: 153891 | 153894 | 153895 | 154065 | 154066 | 154067 | 154087 | 154088 | 154089 | 154090 | 154091 | 154092 | 154419 | 154420