Support request methods selection (#12)

* Fix bug concerning null ApiRateLimit instance in RateLimitHandler

* Support request methods selection

Annotation/ApiRateLimit.php

@@ -28,4 +28,10 @@ final class ApiRateLimit
      * @var array
      */
     public $throttle = [];
+
+    /**
+     * @var array
+     * @example ["GET", "POST"]
+     */
+    public $methods = [];
 }

Resources/doc/usage.md

@@ -101,6 +101,7 @@ Configuration per resource
 -------------------------------
 
 If you wish to configure the rate limits differently on some resources, you can use the `ApiRateLimit` annotation and set the `throttle` property in the same way you do in your main configuration.
+You can define a rate limits only for some specific methods using `methods` property (by default `null` to cover all the different methods).
 You can also choose to enable or disable rate limiting by using the `enabled` property.
 
 ```php
@@ -128,7 +129,8 @@ use Indragunawan\ApiRateLimitBundle\Annotation\ApiRateLimit;
  *                 "period"=10
  *             }
  *         }
- *     }
+ *     },
+ *     methods={"GET", "DELETE"}
  * )
  */
 class Foo

Service/RateLimitHandler.php

@@ -151,6 +151,10 @@ public function handle(Request $request)
 
         if (null !== $annotation) {
             $this->enabled = $annotation->enabled;
+            if (!in_array($request->getMethod(), array_map('strtoupper', $annotation->methods), true) && !empty($annotation->methods)) {
+                // The annotation is ignored as the method is not corresponding
+                $annotation = new ApiRateLimit();
+            }
         } else {
             $annotation = new ApiRateLimit();
         }