chore(KNO-12088): Clarify how empty / not empty treats missing values

[scotidodson]

Clarify how empty and not_empty treat missing values

• State in the operator table that when the variable path is missing, Knock treats it as empty: empty is true, not_empty is false.
• Add a short “Presence, null, and empty” note with an example and when to use exists / not_exists instead.

[linear]

KNO-12088 [Docs] Clarify condition operator meanings

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Mar 16, 2026 9:00pm

[cursor]

Risk LOW: Clarifies empty and not_empty operator descriptions in the conditions reference table to explain how missing variable paths are treated.

Reasons

• Only 1 file changed: content/concepts/conditions.mdx (documentation content)
• Small diff with 19 additions and 19 deletions (table reformatting + two description updates)
• No new pages, sidebar changes, or structural modifications
• No component, layout, or configuration files touched
• Author is a known team member and repository contributor

Notes

• The added sentences for empty and not_empty operators are clear and consistent with the existing style
• No other areas require reviewer attention — this is a straightforward content clarification

  

_{Sent by Cursor Automation: Docs PR classifier}