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
feat(validate): did-you-mean warnings for field typos in flow conditions (#1928) (#1933)
Flow/automation conditions flatten the record's fields to top-level, so a bare
`status` is correct — but a bare NON-field identifier is either a flow variable
or a typo. When it's a near-miss of a known field, the build now emits a
non-blocking `did you mean X?` warning instead of staying silent, closing the
silent-skip gap for misspelled trigger-condition fields (#1877 family) without
the false-positive risk of a hard gate (a real flow variable won't be
edit-distance-close to a field name, so it stays quiet).
- `ExprValidationResult` gains `warnings`; `firstUndeclaredReference(source,
knownFields)` generalizes the bare-ref detector (record scope = no fields,
flattened scope = trigger object's fields declared so only non-field refs
surface).
- `ExprIssue` gains `severity`; `objectstack compile` prints warnings and fails
only on errors.
Verified: a typo'd flow condition warns + still builds; all example apps build
clean with zero warnings (flow variables like `expiring_deals` stay quiet).
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments