You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue. It is a request for a feature that would be nice to have.
In my yaml files there should only be one value per key.
Like so,
KeyA: ValA
Never.
KeyA: ValA ValB
It would be great if there was a rule to set the maximum number of values. Similar to being able to specify the maximum line length. I looked through all the issues and existing rules and could not find such a rule. I apologize if there is one and I missed it.
The text was updated successfully, but these errors were encountered:
The goal of yamllint is to lint the form of YAML, not the content or its structure. We could imagine many new rules to check the number of words in a string value (what you propose), or the type of values, or that all strings contain a substring, or that all keys match a regex, etc. But the purpose of yamllint is to be focused on YAML itself, so I'm not favorable to adding such new content-oriented rules.
To achieve what you want, I would suggest writing a simple script.
This is such a great project. Thank you so much.
This is not an issue. It is a request for a feature that would be nice to have.
In my yaml files there should only be one value per key.
Like so,
KeyA: ValA
Never.
KeyA: ValA ValB
It would be great if there was a rule to set the maximum number of values. Similar to being able to specify the maximum line length. I looked through all the issues and existing rules and could not find such a rule. I apologize if there is one and I missed it.
The text was updated successfully, but these errors were encountered: