Cline rules

1# Strawberry GraphQL Guidelines for GraphQL Filter Demo
2 
3This document outlines the guidelines for using the Strawberry library and implementing the GraphQL schema for the GraphQL Filter Demo project.
4 
5## Schema First Approach
6 
7*   Define the GraphQL schema using Strawberry's type hinting and decorators.
8*   Prioritize clarity and maintainability in the schema definition.
9 
10## VisitaType Consolidation
11 
12*   The API will expose a single `VisitaType` that consolidates relevant fields from the `FatoVisitas` and all dimension tables.
13*   Avoid exposing the underlying data warehouse structure directly to API consumers.
14 
15## InputFilter Implementation
16 
17*   Define generic `InputFilter` types for common data types (String, Int, DateTime, etc.).
18*   Use these generic filters to build the `VisitaFilterInput`.
19*   Ensure the filter logic in the backend correctly translates these filters to SQL `WHERE` clauses on the appropriate dimension table columns.
20 
21## Resolvers
22 
23*   Implement efficient resolvers for the `getVisitas` query.
24*   The resolver should handle the database connection, SQL query construction (including necessary JOINs), and data mapping to `VisitaType`.
25*   Optimize queries to minimize database calls, especially when fetching related dimension data.
26 
27## Error Handling
28 
29*   Implement proper error handling within resolvers.
30*   Return meaningful GraphQL errors for issues like invalid input or database errors.
31 
32## Input Validation
33 
34*   Utilize Strawberry's features or implement custom logic for validating input arguments, especially in filters.
35 
36## Naming Conventions
37 
38*   Follow standard GraphQL naming conventions (PascalCase for types, camelCase for fields).
39*   Align GraphQL field names with the consolidated `VisitaType` representation.
40