Feature Request: Add rule for colons similar to yamllint

[myii]

Taking this example from the epel-formula:

    'common':{

• While this is from map.jinja, something similar could appear in an .sls file.
• The issue here is that there isn't a space after the colon.

Here's the colons rule in yamllint:

• https://yamllint.readthedocs.io/en/stable/rules.html#module-yamllint.rules.colons

While it may be too much to implement the whole rule, even just enforcing (at least) one space after colons should be sufficient.

[jbouter]

I don't think we can just blindly assume there should always be a space after a colon though. It could appear in the contents of a file for example, and be valid. Then again, I guess that's true for most of the checks we perform.

Example:

example_file:
  file.managed:
    - name: /etc/example.txt
    - contents: |
        line:with:colons:without:spaces

[myii]

@jbouter Sure, not after every colon! That's where the linter needs to do it's job to identify the specific places.

[dawidmalina]

It would be very good if we could include all yamllint rules - not only colons.

[dawidmalina]

Proposed test cases:

# the following code snippet would fail:
/path/to/file1:
  file.managed:
    - contents : This is line 1

# the following code snippet would fail:
/path/to/file1:
    file.managed:
      - contents:[]

# the following code snippet would fail:
/path/to/file1:
    file.managed:
      - contents:{}

# the following code snippet would pass:
/path/to/file1:
  file.managed:
    - contents: This is line 1

# the following code snippet would pass:
/path/to/file1:
    file.managed:
      - contents: []

# the following code snippet would pass:
/path/to/file1:
    file.managed:
      - contents: {}

# the following code snippet would pass:
example_file:
  file.managed:
    - name: /etc/example.txt
    - contents: |
        line:with:colons:without:spaces

I will drop pull request this week.

[roaldnefs]

Closing this issue in favour of #240.