Update rfcs/FragmentArguments.md

mjmahone · benjie · web-flow · commit 2dedd5452d8a · 2021-06-03T14:02:17.000-04:00
Co-authored-by: Benjie Gillam &lt;benjie@jemjie.com&gt;
diff --git a/rfcs/FragmentArguments.md b/rfcs/FragmentArguments.md
@@ -203,4 +203,4 @@ This validation rule may end up being more strict than required, but it would be
 
 This proposal can be implemented as a compilation step that compiles the user-written GraphQL into a document without fragment arguments. This can be done in a variety of ways, such as by doing find-variable-replace-with-argument-value or by adding variables on the operation with the argument value set as the default  value.
 
-Alternatively, implementations may want to support fragment arguments directly. For a naive naive approach, during collectFields, when encountering a fragment spread selection for a fragment with argument definitions, replace the argument variables with the passed in argument value or default values.
+Alternatively, implementations may want to support fragment arguments directly. For a naive approach, during collectFields, when encountering a fragment spread selection for a fragment with argument definitions, replace the argument variables with the passed in argument value or default values.

Original file line number	Diff line number	Diff line change
`@@ -203,4 +203,4 @@ This validation rule may end up being more strict than required, but it would be`
`203`	`203`
`204`	`204`	`This proposal can be implemented as a compilation step that compiles the user-written GraphQL into a document without fragment arguments. This can be done in a variety of ways, such as by doing find-variable-replace-with-argument-value or by adding variables on the operation with the argument value set as the default value.`
`205`	`205`
`206`		`-Alternatively, implementations may want to support fragment arguments directly. For a naive naive approach, during collectFields, when encountering a fragment spread selection for a fragment with argument definitions, replace the argument variables with the passed in argument value or default values.`
	`206`	`+Alternatively, implementations may want to support fragment arguments directly. For a naive approach, during collectFields, when encountering a fragment spread selection for a fragment with argument definitions, replace the argument variables with the passed in argument value or default values.`