malloy-debug

Retrieve diagnostics using the ReadLints tool or the Malloy extension's lint output, then fix only the first reported error and re-check. Errors cascade in Malloy, so resolving the earliest one often clears many downstream messages.

Mass cascading errors usually come from using a reserved word like Date, Hour, or number as a field name without backticks. Wrap the identifier in backticks, such as `Date`, and most of the errors will disappear.

Use the having clause instead of where for aggregate filters, for example having: order_count > 10. The where clause cannot reference aggregates, which triggers the "Aggregate not allowed in where" error.

Unknown field errors come from typos, wrong source ordering, referencing the wrong source, or a missing import statement. Check spelling first, then verify the field's source is defined or imported before use.

No, the recommended layout is flat: all .malloy files live in the same package root directory. Use import "orders.malloy" rather than relative paths like "../sources/orders.malloy" to avoid import path errors.