Double check that our code is highest possible quality implementation for the same API it supports now. We should use all the latest versions of dependencies, and latest stable version of rust.
Make sure docs are in sync with code, and fully describe all the features we have in the code.
Double check if it possible to increase tests coverage and docs coverage. And also if it possible to make automated documentation generation as we do in https://github.com/linksplatform/Numbers and https://github.com/linksplatform/trees-rs, and https://github.com/linksplatform/mem-rs, so the final website published in GitHub Pages contains generated documentation for all supported languages. Also code should contain all comments necessary to generate high quality documentation.
Also no tests should be in src folder, use tests folder for tests. All tests found in src folder should be moved in tests folder.
Please fully support best practices of CI/CD from:
If something is missing at https://github.com/link-foundation/rust-ai-driven-development-pipeline-template (make sure to compare full file tree for CI/CD) report the issue there.
So https://github.com/link-foundation/rust-ai-driven-development-pipeline-template will accumulate all the best practices of CI/CD for Rust from all our projects, so it will have highest possible quality and we will need less iterations to make our CI/CD work in all projects.
We need to collect data related about the issue to this repository, make sure we compile that data to ./docs/case-studies/issue-{id} folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), list of each and all requirements from the issue, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).
Double check that our code is highest possible quality implementation for the same API it supports now. We should use all the latest versions of dependencies, and latest stable version of rust.
Make sure docs are in sync with code, and fully describe all the features we have in the code.
Double check if it possible to increase tests coverage and docs coverage. And also if it possible to make automated documentation generation as we do in https://github.com/linksplatform/Numbers and https://github.com/linksplatform/trees-rs, and https://github.com/linksplatform/mem-rs, so the final website published in GitHub Pages contains generated documentation for all supported languages. Also code should contain all comments necessary to generate high quality documentation.
Also no tests should be in src folder, use tests folder for tests. All tests found in src folder should be moved in tests folder.
Please fully support best practices of CI/CD from:
If something is missing at https://github.com/link-foundation/rust-ai-driven-development-pipeline-template (make sure to compare full file tree for CI/CD) report the issue there.
So https://github.com/link-foundation/rust-ai-driven-development-pipeline-template will accumulate all the best practices of CI/CD for Rust from all our projects, so it will have highest possible quality and we will need less iterations to make our CI/CD work in all projects.
We need to collect data related about the issue to this repository, make sure we compile that data to
./docs/case-studies/issue-{id}folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), list of each and all requirements from the issue, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).