Disabled Clippy Lints

[ISTIFANUS-N]

File: /contracts/teachlink/src/lib.rs:1
Severity: Critical
Category: Security & Safety

Description:
The contract uses #![allow(clippy::all)] which disables all Clippy lints, missing critical safety and performance checks.

Acceptance Criteria:

• Remove #![allow(clippy::all)] from all contract files
• Enable and fix all Clippy warnings
• Add Clippy to CI/CD pipeline with fail-on-warnings
• Document linting standards in development guidelines

Impact: High - Potential security vulnerabilities and performance issues

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Copstud3]

@Copstud3 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I can take #132 in rinafcode/teachLink_contract to re-enable Rust linting discipline by removing #![allow(clippy::all)] from /contracts/teachlink/src/lib.rs (and any other contract modules using it), then running cargo clippy and fixing the resulting warnings in a minimal, reviewable way (prefer targeted #[allow(...)] only where there’s a justified, documented exception). I’ll also add a CI step that runs Clippy with fail-on-warnings (e.g., cargo clippy --all-targets --all-features -- -D warnings) so regressions are blocked, and update the project’s development guidelines to define linting standards (required clippy commands, when an allow is acceptable, and how to keep lint fixes security-friendly).

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Copstud3 to this issue.

[drips-wave]

Congratulations, @Copstud3! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Copstud3: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊