Skip to content

[api] Resolve GraphQL stream statuses without collapsing inactive states #1698

Closed

Description

@K1NGD4VID

Labels: api, backend, points: 150
File/location: backend/src/graphql/resolvers/stream.resolver.ts:59

Description:
Every status other than active becomes isActive=false; paused active streams are excluded and cancelled/completed filters return the same mixed records. Unknown statuses are silently accepted.

Acceptance Criteria:

  • Map active, paused, cancelled and completed to their distinct persisted state/event conditions.
  • Reject unknown status values and test mixed fixtures containing every supported state.

Notes:
Executed resolveStreams with status=paused; its database filter was {isActive:false}.

Audited commit: 649b6976a100fd964ce191428eef1faeb50aaa39. Closest prior issues reviewed: #1467. This report concerns the specific failure or uncovered test paths described above, rather than repeating the original feature request.

Activity

  1. Victor123-star commented on Oct 21, 2026

    @Victor123-star

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

    Hi, I’d like to take on this issue.

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

  2. iyiade08 commented on Oct 21, 2026

    @iyiade08

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

    Hi i will love to contribute to this issue and i'll appreciate if it gets assigned to me

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

  3. Rampop01 commented on Oct 21, 2026

    @Rampop01
    Contributor

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

    I would like to work on this issue . I understand the assignment and the requirements, and I’m confident in the approach needed to deliver the best solution. Kindly assign this task to me.

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

  4. drips-wave commented on Oct 21, 2026

    @drips-wave

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

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

  5. Queenode commented on Oct 21, 2026

    @Queenode

    Hi @LabsCrypt team, I have completed the fix for this issue (along with #1699, #1700, and #1701) in branch https://github.com/Rampop01/flowfi/tree/fix/issues-1698-1699-1700-1701. However, opening a pull request to LabsCrypt/flowfi is currently restricted with 'must be a collaborator'. Could you please send a repository collaboration invite or lift the restriction so I can submit the PR? Thanks!

  6. grantfox-oss commented on Oct 22, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @Rampop01's PR #1720 was approved and merged by @blurbeast.

    🏆 @Rampop01: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,228 total points). Track your full progress on GrantFox.

    👏 Great work, @Rampop01! Keep contributing to LabsCrypt.

  7. added a commit that references this issue on Oct 22, 2026
    8872e10
  8. drips-wave commented on Oct 22, 2026

    @drips-wave

    This issue has been completed by @Rampop01 as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @Rampop01: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions