From 519d9fd884e9757af339d4679ea0219f894b8f4d Mon Sep 17 00:00:00 2001 From: Melvyn Date: Sat, 20 Jun 2015 16:48:23 +0200 Subject: [PATCH] code formatting in contributing.md --- doc/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/contributing.md b/doc/contributing.md index f37849b..9696c80 100644 --- a/doc/contributing.md +++ b/doc/contributing.md @@ -33,7 +33,7 @@ The API is structured according to [the command pattern](http://en.wikipedia.org Once you have chosen an API method to work on, you need to do five things before submitting it for inclusion in the API: 1. Create the command in the right folder -2. Implement the command, deriving from `GetAsyncCommandBase` or `PostAsyncCommandBase` (depending on what [the documentation](http://www.last.fm/api) says), and add an ApiMethodNameAttribute on the class, corresponding to the API method you are implementing. (for example, `[ApiMethodName("album.shout")]`) +2. Implement the command, deriving from `GetAsyncCommandBase` or `PostAsyncCommandBase` (depending on what [the documentation](http://www.last.fm/api) says), and add an `ApiMethodNameAttribute` on the class, corresponding to the API method you are implementing. (for example, `[ApiMethodName("album.shout")]`) 3. Create a method on the relevant *Api class 4. Collect sample responses from the API for this method 5. Create a unit test class for the command using the sample responses