Tom Baeyens

Merged here from #1211 : ``` Invalid check "columns types": no viable alternative at input 'columnstypes' +-> checks.yml line=4,col=5 "checks for actor"."[1]"(columns types) Couldn't detect table check type of 'columns...

Merged here from #1199 : @tombaeyens you asked me to file an issue with the situation I had a full on traceback my check was written like so with an...

Merged here from #1194 : For this check, I left out the column name to see what would happen and it errored as expected but maybe the error message could...

Merged here from #1190 A couple of unexpected things with this check. I copy+pasted this out of the docs, changing only the column name and adding the extra check for...

Merged from #1185 Trying to use a warn in a check that uses a statistical metric and it SKIPPED the check. ```yaml checks for sodatest_customers_b7580920: warn: when min(size) >= 0...

Also @janet-can gave input on this earlier: https://sodadata.slack.com/archives/C02J6Q493PY/p1646250277182629 For the CLI output for checks status: why does a warning include the text Only? Only 1 warning. 0 failure. 0 error....

We first need to know if Soda Cloud actually needs this: https://sodadata.slack.com/archives/CAXRR8SS3/p1648647445915439

And https://sodadata.slack.com/archives/C02R6CBF1B8/p1648713724326109

@janet-can if you're able to assist, i'll describe a bit more in detail what the goal of this issue is. The goal is to provide Benjamin & Mathisse with an...

Here's an example of how the check names could be documented for review. Just a suggestion so if you know a better way feel free. ```yaml checks for PRODUCTS: #...