tidal-dl-ng/.github/copilot-instructions.md, branch masterhttp://git.cashmere.rs/tidal-dl-ng/atom/.github/copilot-instructions.md?h=master2025-11-12T13:18:41Zchore: 📝 add comprehensive coding standards and guidelines2025-11-12T13:18:41ZRobert Honzexislow+github@gmail.com2025-11-12T13:18:41Zurn:sha1:554a42860e666f85ac99df6c08c10b3a6f16a5be
* Introduced a new `AGENTS.md` file containing detailed coding standards for the project.
* Covers topics such as Python version support, naming conventions, type annotations, error handling, and best practices.
* Aims to improve code quality, maintainability, and team consistency.
refactor(guidelines): ✨ Improve clarity in coding standards2025-07-02T07:56:57ZRobert Honzexislow+github@gmail.com2025-07-02T07:56:57Zurn:sha1:6d7f4f1625cb57f3d8c58f9b2e07dd759834cc23
* Enhanced wording for better understanding of blank line usage.
* Clarified instructions on updating docstrings during refactoring.
* Specified the use of line comments for complex logic explanations.
refactor(guidelines): ✨ Update coding standards for type annotations2025-07-02T06:49:32ZRobert Honzexislow+github@gmail.com2025-07-02T06:49:32Zurn:sha1:6d62a3b5c040abd9a0a666c5a930fcd5378101f3
* Added a guideline to use modern built-in generics from the `typing` module.
* This change aligns with PEP 484 and promotes better coding practices.
refactor(guidelines): ✨ Update coding standards for type annotations and add PEP references2025-07-01T12:36:37ZRobert Honzexislow+github@gmail.com2025-07-01T12:36:37Zurn:sha1:395771a93904389832e0079531f53db90fdd1ac6
* 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.
chore: 🔧 Update coding standards and documentation guidelines2025-07-01T09:33:04ZRobert Honzexislow+github@gmail.com2025-07-01T09:33:04Zurn:sha1:4dde8c819a82a763e8b5df8a843559a2aafd3e4b
* Refined coding guidelines for clarity and structure.
* Added sections for type annotations and docstring requirements.
* Ensured consistency in documentation practices across the project.
chore: 🔧 Update docstring guidelines for typing usage2025-07-01T09:04:58ZRobert Honzexislow+github@gmail.com2025-07-01T09:04:58Zurn:sha1:1f7d8a15e2a9480976b3a1bc2af84aa939bd2c27
- Added clarification to the docstring guidelines to include the use of `typing` in docstrings.
chore: 🔧 Update coding standards for Python2025-07-01T08:46:41ZRobert Honzexislow+github@gmail.com2025-07-01T08:46:41Zurn:sha1:de47935f049cdab38cbe5ccd665176761ec2c632
- Added a guideline to use the newest coding style supported by the used Python version.
chore: 🔧 Update docstring guidelines in coding standards2025-07-01T08:34:20ZRobert Honzexislow+github@gmail.com2025-07-01T08:34:20Zurn:sha1:ca927984d350328323b7d907067119cc2f19baf6
* Changed "Write docstrings for all public modules, classes, functions, and methods" to "Always write doc strings for all modules, classes, functions, and methods."
* Added missing punctuation for consistency in error handling guidelines.
feat: ✨ Add project coding standards for Python2025-07-01T08:08:46ZRobert Honzexislow+github@gmail.com2025-07-01T08:08:46Zurn:sha1:eda5ab92c010822f638047a657bad6b8eaba3e41
* Introduced guidelines for naming conventions and error handling.
* Specified the use of `snake_case` for variables, `CamelCase` for classes, and PEP 8 compliance.
* Emphasized the importance of type hints and docstrings in code documentation.