Skip to content

BA-114 — Standardize API validation error responses #1027

Open

Description

@MaryammAli

Section: API, health, and shared behavior

Acceptance criteria

Return a stable error code and field details for invalid DTO payloads.

Scope — exactly these 3 files:

  • BackendAcademy/src/main.ts
  • BackendAcademy/src/app.controller.ts
  • BackendAcademy/src/app.controller.spec.ts

Implementation for this issue must be limited to the three files listed above: include implementation, tests, and any necessary types or DTO changes within this three-file allowlist. Do not change any other files.

Activity

  1. Lekan101 commented on Oct 13, 2026

    @Lekan101

    Hello! I’m a smart contract and full-stack developer experienced in Solidity, Cairo, Soroban, TypeScript, and Rust, with contributions across 30+ blockchain projects, including Stellar-based systems. I’m eager to contribute to this issue.

  2. ranjeet150 commented on Oct 13, 2026

    @ranjeet150

    Hello,

    I am interested in taking up "BA-114 — Standardize API validation error responses" and implementing a production-grade solution.

    Technical Implementation Outline:

    1. Review target data structures, error handling (Result/custom errors), and concurrency safety.
    2. Implement resilient, idiomatic Rust logic with zero panics and defensive boundary checks.
    3. Add comprehensive unit and regression tests covering expected behavior and edge cases.
    4. Ensure cargo check, cargo test, and cargo clippy -- -D warnings pass cleanly.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  3. abiolatousin-design commented on Oct 16, 2026

    @abiolatousin-design
    Contributor

    @abiolatousin-design has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi Maintainer, I'll be happy to work on this issue if you will allow me.

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

  4. penielgold-hub commented on Oct 16, 2026

    @penielgold-hub

    @penielgold-hub has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello @MaryammAli,

    I would like to express my interest in Issue #1027 — BA-114: Standardize API Validation Error Responses, under Stellar Wave 10.

    I have practical experience with TypeScript, Node.js, backend API testing, GitHub CI workflows and focused pull-request development.

    My proposed approach:

    1. Review the current NestJS validation and exception-handling implementation.
    2. Introduce a stable validation error code and structured field-level details for invalid DTO payloads.
    3. Integrate the solution with the existing validation pipeline.
    4. Add regression tests covering multiple invalid fields, error consistency and edge cases.
    5. Run the relevant tests and verify that existing API functionality is preserved.

    I will strictly respect the three-file restriction:

    • BackendAcademy/src/main.ts
    • BackendAcademy/src/app.controller.ts
    • BackendAcademy/src/app.controller.spec.ts

    I noticed that PR #1044 already proposes an implementation for this issue, and I would not want to duplicate another contributor's work.

    Could you please confirm whether the issue remains available for assignment or whether additional testing or corrections are required?

    If the task is still available, I would appreciate your consideration for assignment to @penielgold-hub.

    Thank you for your time and consideration.

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

  5. nanajelila800-coder commented on Oct 16, 2026

    @nanajelila800-coder

    @nanajelila800-coder has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I’m excited to apply for this opportunity dear maintainer. kindly see to my application.

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

  6. drips-wave commented on Oct 16, 2026

    @drips-wave

    Congratulations, @nanajelila800-coder! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @nanajelila800-coder: 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 🌊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions