Use "\n"

Author: mglaman

src/Parser/PhpDocParser.php

@@ -89,7 +89,7 @@ private function parseText(TokenIterator $tokens): Ast\PhpDoc\PhpDocTextNode
 			}
 
 			// There's more text on a new line, ensure spacing.
-			$text .= ' ';
+			$text .= "\n";
 		}
 		$text = trim($text, " \t");
 

tests/PHPStan/Parser/PhpDocParserTest.php

@@ -1038,7 +1038,10 @@ public function provideDeprecatedTagsData(): \Iterator
 			new PhpDocNode([
 				new PhpDocTagNode(
 					'@deprecated',
-					new DeprecatedTagValueNode('in Drupal 8.6.0 and will be removed before Drupal 9.0.0. In Drupal 9 there will be no way to set the status and in Drupal 8 this ability has been removed because mb_*() functions are supplied using Symfony\'s polyfill.')
+					new DeprecatedTagValueNode('in Drupal 8.6.0 and will be removed before Drupal 9.0.0. In
+Drupal 9 there will be no way to set the status and in Drupal 8 this
+ability has been removed because mb_*() functions are supplied using
+Symfony\'s polyfill.')
 				),
 			]),
 		];
@@ -1064,7 +1067,10 @@ public function provideDeprecatedTagsData(): \Iterator
 				new PhpDocTextNode(''),
 				new PhpDocTagNode(
 					'@deprecated',
-					new DeprecatedTagValueNode('in Drupal 8.6.0 and will be removed before Drupal 9.0.0. In Drupal 9 there will be no way to set the status and in Drupal 8 this ability has been removed because mb_*() functions are supplied using Symfony\'s polyfill.')
+					new DeprecatedTagValueNode('in Drupal 8.6.0 and will be removed before Drupal 9.0.0. In
+Drupal 9 there will be no way to set the status and in Drupal 8 this
+ability has been removed because mb_*() functions are supplied using
+Symfony\'s polyfill.')
 				),
 			]),
 		];
@@ -1577,7 +1583,8 @@ public function provideMultiLinePhpDocData(): array
 							new IdentifierTypeNode('Foo'),
 							false,
 							'$foo',
-							'1st multi world description some text in the middle'
+							'1st multi world description
+some text in the middle'
 						)
 					),
 					new PhpDocTagNode(
@@ -2301,7 +2308,11 @@ public function provideRealWorldExampleData(): \Iterator
 			'OK with two param and paragraph description',
 			$sample,
 			new PhpDocNode([
-				new PhpDocTextNode('Returns the schema for the field. This method is static because the field schema information is needed on creation of the field. FieldItemInterface objects instantiated at that time are not reliable as field settings might be missing. Computed fields having no schema should return an empty array.'),
+				new PhpDocTextNode('Returns the schema for the field.
+This method is static because the field schema information is needed on
+creation of the field. FieldItemInterface objects instantiated at that
+time are not reliable as field settings might be missing.
+Computed fields having no schema should return an empty array.'),
 		  // @todo the commented out items should be correct.
 		  //new PhpDocTextNode('Returns the schema for the field.'),
 				new PhpDocTextNode(''),
@@ -2317,7 +2328,6 @@ public function provideRealWorldExampleData(): \Iterator
 						''
 					)
 				),
-			// @todo this should be the param description, but new line param descriptions are not handled.
 				new PhpDocTextNode('The field definition.'),
 				new PhpDocTextNode(''),
 				new PhpDocTagNode(
@@ -2327,12 +2337,29 @@ public function provideRealWorldExampleData(): \Iterator
 						''
 					)
 				),
-			// @todo these are actually the @return description.
-				new PhpDocTextNode('An empty array if there is no schema, or an associative array with the following key/value pairs:'),
-				new PhpDocTextNode('- columns: An array of Schema API column specifications, keyed by column name. The columns need to be a subset of the properties defined in propertyDefinitions(). The \'not null\' property is ignored if present, as it is determined automatically by the storage controller depending on the table layout and the property definitions. It is recommended to avoid having the column definitions depend on field settings when possible. No assumptions should be made on how storage engines internally use the original column name to structure their storage.'),
-				new PhpDocTextNode('- unique keys: (optional) An array of Schema API unique key definitions. Only columns that appear in the \'columns\' array are allowed.'),
-				new PhpDocTextNode('- indexes: (optional) An array of Schema API index definitions. Only columns that appear in the \'columns\' array are allowed. Those indexes will be used as default indexes. Field definitions can specify additional indexes or, at their own risk, modify the default indexes specified by the field-type module. Some storage engines might not support indexes.'),
-				new PhpDocTextNode('- foreign keys: (optional) An array of Schema API foreign key definitions. Note, however, that the field data is not necessarily stored in SQL. Also, the possible usage is limited, as you cannot specify another field as related, only existing SQL tables, such as {taxonomy_term_data}.'),
+				new PhpDocTextNode('An empty array if there is no schema, or an associative array with the
+following key/value pairs:'),
+				new PhpDocTextNode('- columns: An array of Schema API column specifications, keyed by column
+name. The columns need to be a subset of the properties defined in
+propertyDefinitions(). The \'not null\' property is ignored if present,
+as it is determined automatically by the storage controller depending
+on the table layout and the property definitions. It is recommended to
+avoid having the column definitions depend on field settings when
+possible. No assumptions should be made on how storage engines
+internally use the original column name to structure their storage.'),
+				new PhpDocTextNode('- unique keys: (optional) An array of Schema API unique key definitions.
+Only columns that appear in the \'columns\' array are allowed.'),
+				new PhpDocTextNode('- indexes: (optional) An array of Schema API index definitions. Only
+columns that appear in the \'columns\' array are allowed. Those indexes
+will be used as default indexes. Field definitions can specify
+additional indexes or, at their own risk, modify the default indexes
+specified by the field-type module. Some storage engines might not
+support indexes.'),
+				new PhpDocTextNode('- foreign keys: (optional) An array of Schema API foreign key
+definitions. Note, however, that the field data is not necessarily
+stored in SQL. Also, the possible usage is limited, as you cannot
+specify another field as related, only existing SQL tables,
+such as {taxonomy_term_data}.'),
 			]),
 		];
 	}