Repository navigation
Code style and linting conventions #551
Description
Activity
@olacodes-01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hi Maintainer, I would like to work on this issue because I understand the problem and have a clear approach to solving it. I look forward to implementing the solution and submitting a clean PR.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @olacodes-01 to this issue.
@johdanike has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
I'd like to tackle this documentation issue. I will draft docs/code-style.md to clearly define the formatting and linting pipelines across TypeScript (Prettier/ESLint), Python (ruff/mypy), and Rust (rustfmt/clippy). I'll ensure the .prettierignore rules for generated files and the house comment conventions are fully covered, alongside how CI gates these rules. Let me know if I'm good to open a PR!
ℹ️ Repo Maintainers: To accept this application, review their application or assign @johdanike to this issue.
Congratulations, @johdanike! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @johdanike: 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 🌊
@Abuh-Bakar has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi maintainer, I would love to work on this. I have implemeted similar solutions on several projects and I can do same here cleanly and efficiently. Allow me the opportunity to contribute to your project while following contribution guidelines for your project. Kindly assign.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abuh-Bakar to this issue.
@KodeSage has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
please assign this issue to me.
I’d like to work on this issue because consistent code style is one of those things that quietly makes a codebase much easier to contribute to and maintain. A clear style guide would give contributors a single reference instead of requiring them to infer conventions from existing files or CI configuration.ℹ️ Repo Maintainers: To accept this application, review their application or assign @KodeSage to this issue.
Congratulations, @KodeSage! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @KodeSage: 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 🌊
Closed by #613, merged into
dev.This issue has been completed by @KodeSage as part of the Stellar Wave Program's 9th Wave 🥳
😎 @KodeSage: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Write
docs/code-style.md: the formatting and lint rules in force per language, how to run them, and the conventions that lint cannot enforce. Cover Prettier (pinned, shared config,.prettierignore), ESLint for TS/TSX,ruff+mypyfor Python, andrustfmt+clippy(with the-D warningsgate) for Rust.Acceptance criteria:
.prettierignoreand the principle behind it — generated output (drizzle meta,.d.ts, Soroban test snapshots) is never formatted