Missing type on boolean inside CASE

[karlhorky]

Describe the bug

The type for the has_url is actually completely empty (empty string) 🤔 Haven't seen this one before.

To Reproduce
Steps to reproduce the behavior:

// 💥 Query has incorrect type annotation.
//	Expected: { has_url: boolean; }
//	Actual: { has_url: ; }[]
await sql<{ has_url: boolean }[]>`
  SELECT
    CASE
      WHEN TRUE THEN personal_intro_url_private IS NOT NULL
      ELSE tech_achievements_url_private IS NOT NULL
    END AS has_url
  FROM
    users
`;

Expected behavior

has_url receives a boolean type, as SafeQL did before the versions released for literal inference:

• Infer TypeScript literals when possible #269

Screenshots

--

Desktop (please complete the following information):

• OS: macOS Sequoia 15.2 (24C101)
• PostgreSQL version 14.13
• Version 3.6.0

Additional context

Problem seems to have been introduced in the versions released for literal inference:

• Infer TypeScript literals when possible #269

[karlhorky]

Confirmed fixed in @ts-safeql/[email protected]:

• fix: handle AExpr and NullTest nodes in SQL parsing #354 (comment)