feat(propdefs): Stricter classification of DateTime values

[eli-r-ph]

Problem

We don't want to accidentally classify large numerical values as DateTime if they happen to match a UNIX timestamp in the last 6 month window.

Changes

Restrict numerical valued DateTime classifications to be both a valid UNIX timestamp in the last 6 months and include one of the "timestamp keywords" in the property name.

All other numerical valued props will be classified as Numeric

Does this work well for both Cloud and self-hosted?

Yes

How did you test this code?

Locally and in CI

[greptile-apps]

PR Summary

This PR refines the classification logic for numeric DateTime properties in the PostHog codebase, ensuring that numerical values are only classified as DateTime when paired with explicit timestamp keywords in their property names.

• Modified logic in /rust/property-defs-rs/src/types.rs to require both a valid UNIX timestamp (within the last 6 months) and a timestamp keyword.
• Prevents large numerical values from being misclassified as DateTime.
• Ensures properties without proper naming conventions default to Numeric, avoiding edge-case misinterpretations.

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}