Files
tidal-dl/.github/copilot-instructions.md
T
Robert Honz 395771a939 refactor(guidelines): ✨ Update coding standards for type annotations and add PEP references
* Clarified type annotations usage for function parameters, return types, and variables.
* Added guidelines for using blank lines, coroutines, and string interpolation as per PEP standards.
2025-07-01 14:36:37 +02:00

1.0 KiB
Raw Blame History

applyTo
applyTo
**/*.py

Project general coding standards

Naming Conventions

  • Use snake_case for variable and function names.
  • Use CamelCase for class names.
  • Follow PEP 8 style guidelines.
  • Prefix private class members with underscore (_).
  • Use ALL_CAPS for constants.

Error Handling

  • Use try/except blocks for async operations.
  • Always log errors with contextual information.

Coding Guidelines

  • Use type annotations / hints for function and method parameters, return types and variables. Follow PEP 484.
  • Use newest coding style which is supported by the used Python version.
  • Use blank lines to keep code organized and readable.
  • Follow PEP 492 – Coroutines with async and await syntax
  • Follow PEP 498 – Literal String Interpolation
  • Follow PEP 572 – Assignment Expressions

Code Documentation

  • Always write doc strings for all modules, classes, functions, and methods using google docstring style.
  • Use typing in doc strings.
  • Use short inline comments to explain complex logic.