Adopt identical YAML formatting for info.yml files

.

I think that this is a good idea, but first we need to set this to 8.3.x dev. I'm going to assign this to myself and start working on it. The data is quite outdated though. Here is a new set:

$ for i in "name: " "name: '" ; do grep "$i" */*.info.yml | wc -l | xargs echo Number of occurences for string "\"$i\"" =\> ; done ; for i in "description: " "description: '" ; do grep "$i" */*.info.yml | wc -l | xargs echo Number of occurences for string "\"$i\"" =\> ; done ;
Number of occurences for string "name: " => 72
Number of occurences for string "name: '" => 23
Number of occurences for string "description: " => 72
Number of occurences for string "description: '" => 68

Here is the patch for removing quotes from names and for adding them to description as suggested by reporter. If ever its decided to remove quotes for description as well, then I'd be happy to make another patch :)

Here's the interdiff :)

I personally do it this way: As soon as a string contains a space then I enclose the string in single quotes. That is what the Symfoner YAML encoder does, so this makes various handcrafted YAMLs nicely consistent with exported configuration.

I'm wondering whether we could/should integrate this into a phpcs rule, so for example contrib modules don't have to think about it, but rather just check the rules.

@dawehner I don't think we should force this on them as it might render some modules unusable. I'd rather that we adopt this as a standard...

+++ b/core/modules/basic_auth/basic_auth.info.yml
@@ -1,6 +1,6 @@
-description: 'Provides the HTTP Basic authentication provider.'
+description: 'Provides the HTTP Basic authentication provider'

+++ a/core/modules/datetime/datetime.info.yml
@@ -1,6 +1,6 @@
+description: Defines datetime form elements and a datetime field type.
-description: 'Defines datetime form elements and a datetime field type.'

+++ a/core/modules/serialization/serialization.info.yml
@@ -1,6 +1,6 @@
+description: Provides a service for (de)serializing data to/from formats such as JSON and XML
-description: 'Provides a service for (de)serializing data to/from formats such as JSON and XML.'
...

There are descriptions which were not enclosed in single quotes. Plus, some of them don't have a period (.) at the end.

it might render some modules unusable

It won't. Adding it into a phpcs rule will only let developers know they are not following the standards if they check their code.

@gvso thanks for the review! Here is a patch and its interdiff for fixing the few decriptions that were not edited. If phpcs won't break anything(forgive my noob knowledge), then sure, somebody please implement it!

@Kifah Meeran, I guess we need to decide which convention we are going to follow first before working on a patch.

Closing this as a duplicate of #2994928: Quote consistency in .info.yml files for Core modules

Looks like I forgot to change the status here. I did move credit.