From 1f1071a8c38b3e1d8b33a11df3b4073a9034616c Mon Sep 17 00:00:00 2001 From: Jesse Skinner Date: Sun, 21 Sep 2014 23:00:25 -0400 Subject: [PATCH] Fix inconsistency in mockComponent argument name The second argument of mockComponent was listed as tagName, but referred to in the description as mockTagName. I changed the first one to mockTagName to be consistent. --- docs/09.4-test-utils.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/09.4-test-utils.md b/docs/09.4-test-utils.md index 18c634959..2eec1d23c 100644 --- a/docs/09.4-test-utils.md +++ b/docs/09.4-test-utils.md @@ -38,7 +38,7 @@ Render a component into a detached DOM node in the document. **This function req ### mockComponent ```javascript -object mockComponent(function componentClass, string? tagName) +object mockComponent(function componentClass, string? mockTagName) ``` Pass a mocked component module to this method to augment it with useful methods that allow it to be used as a dummy React component. Instead of rendering as usual, the component will become a simple `
` (or other tag if `mockTagName` is provided) containing any provided children.