Cline rules

1# Python Best Practices for GraphQL Filter Demo
2 
3This document outlines the Python best practices to be followed during the development of the GraphQL Filter Demo project.
4 
5## PEP 8 Compliance
6 
7*   Adhere to PEP 8 style guide for code formatting.
8*   Use a linter (like Flake8 or Pylint) and formatter (like Black or autopep8) to ensure compliance.
9 
10## Type Hinting
11 
12*   Use type hints for function arguments, return values, and variables to improve code readability and maintainability.
13*   Utilize tools like MyPy for static type checking.
14 
15## Docstrings
16 
17*   Write clear and concise docstrings for all modules, classes, methods, and functions.
18*   Follow a consistent docstring format (e.g., Google, NumPy, or reST style).
19 
20## Modularity and Organization
21 
22*   Organize code into logical modules and packages.
23*   Keep functions and classes small and focused on a single responsibility.
24 
25## Error Handling
26 
27*   Use exceptions for error handling.
28*   Catch specific exceptions rather than broad `except Exception:` clauses.
29*   Provide informative error messages.
30 
31## Naming Conventions
32 
33*   Use descriptive names for variables, functions, classes, and modules.
34*   Follow PEP 8 naming conventions (snake_case for functions/variables, PascalCase for classes).
35 
36## Imports
37 
38*   Organize imports at the top of the file.
39*   Group imports in the following order: standard library, third-party libraries, local application/library specific imports.
40*   Use absolute imports where possible.
41 
42## Testing
43 
44*   Write tests for your code (unit tests, integration tests).
45*   Aim for good test coverage.
46