Naming policy test: SQL timestamps should end with _at.

[isoos]

• related to Unroll TaskState into two new SQL table (write-only for now). #9485
• exempting the already failing columns

[sigurdm]

Is there a specific reason for this convention? Does it help us? Are the fields not already statically strongly typed in dart?

[isoos]

Is there a specific reason for this convention?

LLM suggestion after reviewing the column names.

Does it help us? Are the fields not already statically strongly typed in dart?

I think it does, if for nothing else, it improves consistency. It is also somewhat confusing the have both scheduled and finished and you don't know if it is a boolean (isScheduled and isFinished) or a timestamp (scheduledAt and finishedAt).

[sigurdm]

I don't mind either way

[jonasfj]

If you want this better, consider using package:stringscanner and make dump using a SourceSpan when there is an issue. That way we won't spend so much time figuring out what is wrong when we hit it.

[isoos]

If you want this better, consider using package:stringscanner and make dump using a SourceSpan when there is an issue. That way we won't spend so much time figuring out what is wrong when we hit it.

Let's consider this when we could have more rules like this one, until then the simple may be enough.