feat(parse): comment_no_infix option

Author: wdavidw

csv

@@ -31,6 +31,9 @@ All options are optional. The options from the [Node.js Stream Writable](https:/
 * [`comment`](/parse/options/comment/) (string|buffer)   
   _Since early days_   
   Treat all the characters after this one as a comment; one or multiple characters; disabled by default by defining an empty string `""`.
+* [`comment_no_infix`](/parse/options/comment_no_infix/) (boolean)   
+  _Since 5.5.0_   
+  Restricts the definition of comments to full lines.
 * [`delimiter`](/parse/options/delimiter/) (string|Buffer|[string|Buffer])   
   _Since version 0.0.1_   
   Set one or several field delimiters containing one or several characters. It defaults to `,` (comma).

src/md/parse/options.md

@@ -0,0 +1,24 @@
+---
+title: Option comment_no_infix
+navtitle: comment_no_infix
+description: Option "columns" generate records as object literals instead of arrays.
+keywords: ['csv', 'parse', 'options', 'columns']
+---
+
+# Option `comment_no_infix`
+
+The `comment_no_infix` option restricts the definition of comments to full lines. Comment characters defined in the middle of a line are not interpreted as such.
+
+Comments are disabled by default. Thus, this option only takes effect when comments are activated.
+
+* Type: `boolean`
+* Optional
+* Default: `false`
+* Since: `5.5.0`
+* Related: [`comment`](/parse/options/comment/) — see [Available Options](/parse/options/#available-options)
+
+## Example
+
+While the default behavior generates `[ [ 'a', 'b' ] ]`, activating `comment_no_infix` in the example below disregards the comment character present in the second line.
+
+`embed:packages/csv-parse/samples/option.comment_no_infix.js`