Docs/WordPress.WhiteSpace.OperatorSpacing

[ckanitz]

Adds documentation for the WordPress.WhiteSpace.OperatorSpacing

Related to #1722

[jrfnl]

@ckanitz Hi Christopher, mostly looking very good.

The docs are just missing the <em> ...</em> tags to highlight good/bad code, but we weren't that clear about that in the initial explanation, so sorry about that!.

Other than that one more point:
It is customary to have a Valid | Invalid code comparison.
The code comparisons you are doing here are Valid | Valid / Invalid | Invalid.

Just thinking out loud: you could possibly combine the two "invalid" examples into one with an inline comment to separate them // Too little space, // Too much space and place that one to go with the first Valid example.

For the second Valid example, the same code sample as for the Valid case can be used with some superfluous whitespace after the && on the second line.

What do you think ?

[ckanitz]

Just thinking out loud: you could possibly combine the two "invalid" examples into one with an inline comment to separate them // Too little space, // Too much space and place that one to go with the first Valid example.

For the second Valid example, the same code sample as for the Valid case can be used with some superfluous whitespace after the && on the second line.

What do you think ?

Sounds good to me! I applied the changes as suggested.

[jrfnl]

@ckanitz Hi Christopher, thank you for making those changes!

Nearly there. I've had a second look and saw some things I missed the first time around. Sorry about that.
Nothing major though, just some small tweaks to finish it off.

I look forward to being able to merge this soon.

[jrfnl]

@ckanitz Just wondering if you'll have a chance to finish this off in the near future.
I'd like to release WPCS 2.2.0 soon and it would be great if this PR could be included.

If you haven't got time or lost interest, please let us know and we'll see if we can find someone to take over.

[jrfnl]

I've rebased the PR and added one commit to make the last fixes needed. Let's get this merged!

For whomever will merge this: probably squash/merge would be a good idea.