From bea243a0cadc36b481a36931f29e4c321f54a36b Mon Sep 17 00:00:00 2001 From: Xavier Ordoquy Date: Mon, 18 Jul 2016 16:56:36 +0200 Subject: [PATCH] Fix coreapi param arguments. (#4274) --- docs/tutorial/7-schemas-and-client-libraries.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tutorial/7-schemas-and-client-libraries.md b/docs/tutorial/7-schemas-and-client-libraries.md index c2141489c..77cfdd3b3 100644 --- a/docs/tutorial/7-schemas-and-client-libraries.md +++ b/docs/tutorial/7-schemas-and-client-libraries.md @@ -126,7 +126,7 @@ Let's try listing the existing snippets, using the command line client: Some of the API endpoints require named parameters. For example, to get back the highlight HTML for a particular snippet we need to provide an id. - $ coreapi action snippets highlight --param pk 1 + $ coreapi action snippets highlight --param pk=1 @@ -168,7 +168,7 @@ set of available interactions. We're now able to interact with these endpoints. For example, to create a new snippet: - $ coreapi action snippets create --param title "Example" --param code "print('hello, world')" + $ coreapi action snippets create --param title="Example" --param code="print('hello, world')" { "url": "http://127.0.0.1:8000/snippets/7/", "pk": 7, @@ -183,7 +183,7 @@ snippet: And to delete a snippet: - $ coreapi action snippets destroy --param pk 7 + $ coreapi action snippets destroy --param pk=7 As well as the command line client, developers can also interact with your API using client libraries. The Python client library is the first of these