From 3c53a4de5b80c163df7d0b04d2bb19bf9ae03b3c Mon Sep 17 00:00:00 2001
From: Daniel Siepmann <coding@daniel-siepmann.de>
Date: Mon, 6 Mar 2017 11:38:43 +0100
Subject: [PATCH] BUGFIX: Add missing argumentName

* As this is not mandantory.
---
 Documentation/source/index.rst | 2 +-
 Documentation/source/usage.rst | 4 ++--
 README.md                      | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/source/index.rst b/Documentation/source/index.rst
index b3fcf0f..ddafd6a 100644
--- a/Documentation/source/index.rst
+++ b/Documentation/source/index.rst
@@ -12,7 +12,7 @@ Lets imagine you have this action-method::
 
     /**
      * @param Order $order
-     * @Flow\Validate(type="DigiComp.SettingValidator:Settings")
+     * @Flow\Validate(type="DigiComp.SettingValidator:Settings", argumentName="$order")
      */
     public function createOrder(Order $order) {...}
 
diff --git a/Documentation/source/usage.rst b/Documentation/source/usage.rst
index 74a065a..8b4e201 100644
--- a/Documentation/source/usage.rst
+++ b/Documentation/source/usage.rst
@@ -33,7 +33,7 @@ If you prefer the name, you have to configure the validator to use the specific
 
     /**
      * @param OrderCustomer $orderCustomer
-     * @Flow\Validate(argumentName="orderCustomer", type="DigiComp.SettingValidator:Settings", options={"name"="OrderCustomer"})
+     * @Flow\Validate(argumentName="$orderCustomer", type="DigiComp.SettingValidator:Settings", options={"name"="OrderCustomer"})
      */
     public function createOrder(OrderCustomer $orderCustomer) {...}
 
@@ -47,7 +47,7 @@ argument, the following code will be enough::
 
     /**
      * @param Order $order
-     * @Flow\Validate(argumentName="order, type="DigiComp.SettingValidator:Settings")
+     * @Flow\Validate(argumentName="$order, type="DigiComp.SettingValidator:Settings")
      */
     public function createOrder(Order $order) {...}
 
diff --git a/README.md b/README.md
index f5fae0b..ac8e063 100644
--- a/README.md
+++ b/README.md
@@ -9,7 +9,7 @@ Lets imagine you had this action-method:
 
 	/**
 	 * @param Order $order
-	 * @Flow\Validate(type="DigiComp.SettingValidator:Settings")
+	 * @Flow\Validate(type="DigiComp.SettingValidator:Settings", argumentName="$order")
 	 */
 	public function createOrder($order) {...}
 
@@ -43,4 +43,4 @@ Then your Validation.yaml could look like this:
 As you see: Nesting is possible ;) That way you can easily construct flexible structures.
 
 The SettingsValidator has an optional option: "name" - If you don't give one, it assumes your validation value is an
-object and searches in Validation.yaml for the FQCN.
\ No newline at end of file
+object and searches in Validation.yaml for the FQCN.