flutter-query-lint

You can validate Flutter Supabase queries by running a linter script that cross-references your API files against `database.types.ts`. This process checks table names, columns, and relationships to prevent runtime errors before deployment.

Supabase query validation verifies that table names, columns, and `.rpc()` calls in your Flutter code match the actual database schema definition. It identifies mismatches early to ensure code integrity and prevent user-facing failures.

Yes, you can check for non-existent tables and columns by cross-referencing your Flutter API files with `database.types.ts`. The linter identifies and reports schema mismatches, making it ideal for catching errors before merging a pull request.

You verify Supabase RPC function calls by running a linter that checks your Flutter code against existing database functions. It ensures that every `.rpc()` call corresponds to a defined function in your database schema.

Yes, you need a `database.types.ts` file to lint Supabase queries effectively. The linter uses this database schema definition as the source of truth to validate tables, columns, and RPC functions referenced in your Flutter API files.