Support for Yaml

[jborgers]

Configuration is typically done in Yaml files these days.

YAML has broad language support and maps easily into native data structures. It's also easy for humans to read, which is why it's a good choice for configuration.

PMD has support for XML, however, not for yaml.

I'd like to detect configuration mistakes for instance in resilience4j circuit-breaker configuration, by having / making rules for it.

Are you considering to add support for Yaml? Would it be much work?

Experience with adding Kotlin was that it was rather much work. Maybe this case is simpler and less work?

[jborgers]

Rules could be for instance be DurationInRangeCheck as template rule.
Mistakes can be made for instance with timeouts assuming the wrong unit of time.

[jborgers]

Anyone? @adangel?

[UncleOwen]

I fear this will run into the "only one language per extension problem" really fast. If I understand you correctly, you don't want "Yaml" as a language, you want "resilience4j circuit-breaker configuration", right?

(XML has the same problem)

That being said, PRs are always welcome.

[jborgers]

@UncleOwen Not really. The rules should be generic enough not to be resilience4j specific. And they should be configurable, possibly through templating, to become specific.

[jborgers]

Like: RequiredKeyCheck, IntValueInRangeCheck, DurationInRangeCheck, we have in https://github.com/sbaudoin/sonar-yaml.
However, it seems that project is dead. My PR is waiting there for more than 1.5 years.