Skip to content

ghit-issues-25.md

Latest commit

 

History

History
1289 lines (1049 loc) · 49.6 KB

ghit-issues-25.md

File metadata and controls

1289 lines (1049 loc) · 49.6 KB
Raw
type Feature
title Propagate a correlation/trace id through the contracts flow
labels type:feature, area:contracts, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26
assignees

Trace contracts requests

Description

contracts requests can't be traced across layers, slowing incident triage. This issue propagates a correlation id end to end.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Accept/generate a correlation id on contracts requests and thread it through logs and downstream calls.
  • Return it in responses/errors for support.
  • Cover propagation in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/contracts-41-trace
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: generated when absent, echoed, present in logs.
  • Include the full test output in the PR description.

Example commit message

feat(contracts): propagate correlation id

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Gate contracts behind a feature flag" labels: type:feature, area:contracts, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Feature-flag contracts

Description

New contracts behavior can't be toggled without a deploy. This issue adds a config feature flag around it.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add a config/env feature flag that enables/disables the contracts behavior at runtime with a safe default.
  • Cover both enabled and disabled paths in tests.
  • Document the flag.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/contracts-42-flag
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: flag on, flag off, default.
  • Include the full test output in the PR description.

Example commit message

feat(contracts): add feature flag

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add regression tests for known contracts edge cases" labels: type:test, area:contracts, stack:nodejs, stack:typescript, priority:high, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Regression-test contracts

Description

Previously-fixed contracts edge cases lack guards, risking re-breakage. This issue adds regression tests.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add tests reproducing the tricky contracts edge cases (empty, boundary, malformed) so they can't regress.
  • Reference the scenarios in test names.
  • Fix any still-broken case (note it).

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b test/contracts-41-regression
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: empty, boundary, malformed inputs.
  • Include the full test output in the PR description.

Example commit message

test(contracts): add edge-case regression tests

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add validation schemas for contracts request/response payloads" labels: type:refactor, area:contracts, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Schema-validate contracts

Description

contracts payloads are validated ad hoc. This issue introduces declarative schemas for consistent validation.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Define request/response schemas for contracts and validate against them at the boundary.
  • Reject invalid payloads with structured errors; behaviour otherwise unchanged.
  • Cover valid/invalid in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b refactor/contracts-41-schema
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: valid passes, invalid rejected with details.
  • Include the full test output in the PR description.

Example commit message

refactor(contracts): add validation schemas

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add copy-paste example requests for the contracts endpoints" labels: type:docs, area:contracts, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Examples for contracts

Description

The contracts endpoints lack ready-to-run examples. This issue adds curl/HTTP examples.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add docs/contracts-examples.md with runnable request/response examples for each contracts endpoint.
  • Keep them accurate; note required headers/auth.
  • Verify each example against the route.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b docs/contracts-41-examples
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: n/a — verify examples against routes.
  • Include the full test output in the PR description.

Example commit message

docs(contracts): add request examples

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Propagate a correlation/trace id through the milestones flow" labels: type:feature, area:milestones, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Trace milestones requests

Description

milestones requests can't be traced across layers, slowing incident triage. This issue propagates a correlation id end to end.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Accept/generate a correlation id on milestones requests and thread it through logs and downstream calls.
  • Return it in responses/errors for support.
  • Cover propagation in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/milestones-41-trace
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: generated when absent, echoed, present in logs.
  • Include the full test output in the PR description.

Example commit message

feat(milestones): propagate correlation id

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Gate milestones behind a feature flag" labels: type:feature, area:milestones, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Feature-flag milestones

Description

New milestones behavior can't be toggled without a deploy. This issue adds a config feature flag around it.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add a config/env feature flag that enables/disables the milestones behavior at runtime with a safe default.
  • Cover both enabled and disabled paths in tests.
  • Document the flag.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/milestones-42-flag
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: flag on, flag off, default.
  • Include the full test output in the PR description.

Example commit message

feat(milestones): add feature flag

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add regression tests for known milestones edge cases" labels: type:test, area:milestones, stack:nodejs, stack:typescript, priority:high, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Regression-test milestones

Description

Previously-fixed milestones edge cases lack guards, risking re-breakage. This issue adds regression tests.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add tests reproducing the tricky milestones edge cases (empty, boundary, malformed) so they can't regress.
  • Reference the scenarios in test names.
  • Fix any still-broken case (note it).

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b test/milestones-41-regression
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: empty, boundary, malformed inputs.
  • Include the full test output in the PR description.

Example commit message

test(milestones): add edge-case regression tests

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add validation schemas for milestones request/response payloads" labels: type:refactor, area:milestones, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Schema-validate milestones

Description

milestones payloads are validated ad hoc. This issue introduces declarative schemas for consistent validation.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Define request/response schemas for milestones and validate against them at the boundary.
  • Reject invalid payloads with structured errors; behaviour otherwise unchanged.
  • Cover valid/invalid in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b refactor/milestones-41-schema
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: valid passes, invalid rejected with details.
  • Include the full test output in the PR description.

Example commit message

refactor(milestones): add validation schemas

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add copy-paste example requests for the milestones endpoints" labels: type:docs, area:milestones, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Examples for milestones

Description

The milestones endpoints lack ready-to-run examples. This issue adds curl/HTTP examples.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add docs/milestones-examples.md with runnable request/response examples for each milestones endpoint.
  • Keep them accurate; note required headers/auth.
  • Verify each example against the route.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b docs/milestones-41-examples
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: n/a — verify examples against routes.
  • Include the full test output in the PR description.

Example commit message

docs(milestones): add request examples

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Propagate a correlation/trace id through the reputation flow" labels: type:feature, area:reputation, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Trace reputation requests

Description

reputation requests can't be traced across layers, slowing incident triage. This issue propagates a correlation id end to end.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Accept/generate a correlation id on reputation requests and thread it through logs and downstream calls.
  • Return it in responses/errors for support.
  • Cover propagation in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/reputation-41-trace
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: generated when absent, echoed, present in logs.
  • Include the full test output in the PR description.

Example commit message

feat(reputation): propagate correlation id

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Gate reputation behind a feature flag" labels: type:feature, area:reputation, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Feature-flag reputation

Description

New reputation behavior can't be toggled without a deploy. This issue adds a config feature flag around it.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add a config/env feature flag that enables/disables the reputation behavior at runtime with a safe default.
  • Cover both enabled and disabled paths in tests.
  • Document the flag.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/reputation-42-flag
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: flag on, flag off, default.
  • Include the full test output in the PR description.

Example commit message

feat(reputation): add feature flag

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add regression tests for known reputation edge cases" labels: type:test, area:reputation, stack:nodejs, stack:typescript, priority:high, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Regression-test reputation

Description

Previously-fixed reputation edge cases lack guards, risking re-breakage. This issue adds regression tests.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add tests reproducing the tricky reputation edge cases (empty, boundary, malformed) so they can't regress.
  • Reference the scenarios in test names.
  • Fix any still-broken case (note it).

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b test/reputation-41-regression
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: empty, boundary, malformed inputs.
  • Include the full test output in the PR description.

Example commit message

test(reputation): add edge-case regression tests

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add validation schemas for reputation request/response payloads" labels: type:refactor, area:reputation, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Schema-validate reputation

Description

reputation payloads are validated ad hoc. This issue introduces declarative schemas for consistent validation.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Define request/response schemas for reputation and validate against them at the boundary.
  • Reject invalid payloads with structured errors; behaviour otherwise unchanged.
  • Cover valid/invalid in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b refactor/reputation-41-schema
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: valid passes, invalid rejected with details.
  • Include the full test output in the PR description.

Example commit message

refactor(reputation): add validation schemas

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add copy-paste example requests for the reputation endpoints" labels: type:docs, area:reputation, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Examples for reputation

Description

The reputation endpoints lack ready-to-run examples. This issue adds curl/HTTP examples.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add docs/reputation-examples.md with runnable request/response examples for each reputation endpoint.
  • Keep them accurate; note required headers/auth.
  • Verify each example against the route.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b docs/reputation-41-examples
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: n/a — verify examples against routes.
  • Include the full test output in the PR description.

Example commit message

docs(reputation): add request examples

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Propagate a correlation/trace id through the disputes flow" labels: type:feature, area:disputes, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Trace disputes requests

Description

disputes requests can't be traced across layers, slowing incident triage. This issue propagates a correlation id end to end.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Accept/generate a correlation id on disputes requests and thread it through logs and downstream calls.
  • Return it in responses/errors for support.
  • Cover propagation in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/disputes-41-trace
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: generated when absent, echoed, present in logs.
  • Include the full test output in the PR description.

Example commit message

feat(disputes): propagate correlation id

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Gate disputes behind a feature flag" labels: type:feature, area:disputes, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Feature-flag disputes

Description

New disputes behavior can't be toggled without a deploy. This issue adds a config feature flag around it.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add a config/env feature flag that enables/disables the disputes behavior at runtime with a safe default.
  • Cover both enabled and disabled paths in tests.
  • Document the flag.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/disputes-42-flag
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: flag on, flag off, default.
  • Include the full test output in the PR description.

Example commit message

feat(disputes): add feature flag

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add regression tests for known disputes edge cases" labels: type:test, area:disputes, stack:nodejs, stack:typescript, priority:high, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Regression-test disputes

Description

Previously-fixed disputes edge cases lack guards, risking re-breakage. This issue adds regression tests.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add tests reproducing the tricky disputes edge cases (empty, boundary, malformed) so they can't regress.
  • Reference the scenarios in test names.
  • Fix any still-broken case (note it).

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b test/disputes-41-regression
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: empty, boundary, malformed inputs.
  • Include the full test output in the PR description.

Example commit message

test(disputes): add edge-case regression tests

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add validation schemas for disputes request/response payloads" labels: type:refactor, area:disputes, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Schema-validate disputes

Description

disputes payloads are validated ad hoc. This issue introduces declarative schemas for consistent validation.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Define request/response schemas for disputes and validate against them at the boundary.
  • Reject invalid payloads with structured errors; behaviour otherwise unchanged.
  • Cover valid/invalid in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b refactor/disputes-41-schema
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: valid passes, invalid rejected with details.
  • Include the full test output in the PR description.

Example commit message

refactor(disputes): add validation schemas

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add copy-paste example requests for the disputes endpoints" labels: type:docs, area:disputes, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Examples for disputes

Description

The disputes endpoints lack ready-to-run examples. This issue adds curl/HTTP examples.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add docs/disputes-examples.md with runnable request/response examples for each disputes endpoint.
  • Keep them accurate; note required headers/auth.
  • Verify each example against the route.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b docs/disputes-41-examples
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: n/a — verify examples against routes.
  • Include the full test output in the PR description.

Example commit message

docs(disputes): add request examples

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Propagate a correlation/trace id through the audit flow" labels: type:feature, area:audit, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Trace audit requests

Description

audit requests can't be traced across layers, slowing incident triage. This issue propagates a correlation id end to end.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Accept/generate a correlation id on audit requests and thread it through logs and downstream calls.
  • Return it in responses/errors for support.
  • Cover propagation in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/audit-41-trace
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: generated when absent, echoed, present in logs.
  • Include the full test output in the PR description.

Example commit message

feat(audit): propagate correlation id

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Gate audit behind a feature flag" labels: type:feature, area:audit, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Feature-flag audit

Description

New audit behavior can't be toggled without a deploy. This issue adds a config feature flag around it.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add a config/env feature flag that enables/disables the audit behavior at runtime with a safe default.
  • Cover both enabled and disabled paths in tests.
  • Document the flag.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/audit-42-flag
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: flag on, flag off, default.
  • Include the full test output in the PR description.

Example commit message

feat(audit): add feature flag

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add regression tests for known audit edge cases" labels: type:test, area:audit, stack:nodejs, stack:typescript, priority:high, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Regression-test audit

Description

Previously-fixed audit edge cases lack guards, risking re-breakage. This issue adds regression tests.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add tests reproducing the tricky audit edge cases (empty, boundary, malformed) so they can't regress.
  • Reference the scenarios in test names.
  • Fix any still-broken case (note it).

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b test/audit-41-regression
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: empty, boundary, malformed inputs.
  • Include the full test output in the PR description.

Example commit message

test(audit): add edge-case regression tests

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add validation schemas for audit request/response payloads" labels: type:refactor, area:audit, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Schema-validate audit

Description

audit payloads are validated ad hoc. This issue introduces declarative schemas for consistent validation.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Define request/response schemas for audit and validate against them at the boundary.
  • Reject invalid payloads with structured errors; behaviour otherwise unchanged.
  • Cover valid/invalid in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b refactor/audit-41-schema
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: valid passes, invalid rejected with details.
  • Include the full test output in the PR description.

Example commit message

refactor(audit): add validation schemas

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add copy-paste example requests for the audit endpoints" labels: type:docs, area:audit, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Examples for audit

Description

The audit endpoints lack ready-to-run examples. This issue adds curl/HTTP examples.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add docs/audit-examples.md with runnable request/response examples for each audit endpoint.
  • Keep them accurate; note required headers/auth.
  • Verify each example against the route.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b docs/audit-41-examples
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: n/a — verify examples against routes.
  • Include the full test output in the PR description.

Example commit message

docs(audit): add request examples

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Propagate a correlation/trace id through the webhooks flow" labels: type:feature, area:webhooks, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Trace webhooks requests

Description

webhooks requests can't be traced across layers, slowing incident triage. This issue propagates a correlation id end to end.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Accept/generate a correlation id on webhooks requests and thread it through logs and downstream calls.
  • Return it in responses/errors for support.
  • Cover propagation in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/webhooks-41-trace
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: generated when absent, echoed, present in logs.
  • Include the full test output in the PR description.

Example commit message

feat(webhooks): propagate correlation id

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Gate webhooks behind a feature flag" labels: type:feature, area:webhooks, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Feature-flag webhooks

Description

New webhooks behavior can't be toggled without a deploy. This issue adds a config feature flag around it.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add a config/env feature flag that enables/disables the webhooks behavior at runtime with a safe default.
  • Cover both enabled and disabled paths in tests.
  • Document the flag.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b feature/webhooks-42-flag
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: flag on, flag off, default.
  • Include the full test output in the PR description.

Example commit message

feat(webhooks): add feature flag

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add regression tests for known webhooks edge cases" labels: type:test, area:webhooks, stack:nodejs, stack:typescript, priority:high, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Regression-test webhooks

Description

Previously-fixed webhooks edge cases lack guards, risking re-breakage. This issue adds regression tests.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add tests reproducing the tricky webhooks edge cases (empty, boundary, malformed) so they can't regress.
  • Reference the scenarios in test names.
  • Fix any still-broken case (note it).

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b test/webhooks-41-regression
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: empty, boundary, malformed inputs.
  • Include the full test output in the PR description.

Example commit message

test(webhooks): add edge-case regression tests

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add validation schemas for webhooks request/response payloads" labels: type:refactor, area:webhooks, stack:nodejs, stack:typescript, priority:medium, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Schema-validate webhooks

Description

webhooks payloads are validated ad hoc. This issue introduces declarative schemas for consistent validation.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Define request/response schemas for webhooks and validate against them at the boundary.
  • Reject invalid payloads with structured errors; behaviour otherwise unchanged.
  • Cover valid/invalid in tests.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b refactor/webhooks-41-schema
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: valid passes, invalid rejected with details.
  • Include the full test output in the PR description.

Example commit message

refactor(webhooks): add validation schemas

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated. ++++++

type: Feature title: "Add copy-paste example requests for the webhooks endpoints" labels: type:docs, area:webhooks, stack:nodejs, stack:typescript, priority:low, Stellar Wave, MAYBE REWARDED, GRANTFOX OSS, OFFICIAL CAMPAIGN, Official Campaign | FWC26 assignees: ''

Examples for webhooks

Description

The webhooks endpoints lack ready-to-run examples. This issue adds curl/HTTP examples.

Requirements and context

  • Repository scope: Talenttrust/Talenttrust-Backend only.
  • Add docs/webhooks-examples.md with runnable request/response examples for each webhooks endpoint.
  • Keep them accurate; note required headers/auth.
  • Verify each example against the route.

Suggested execution

  • Fork the repo and create a branch
  • git checkout -b docs/webhooks-41-examples
  • Implement changes
    • Write code in: the relevant module.
    • Write comprehensive tests in: cover the new behaviour and edge cases.
  • Test and commit

Test and commit

  • Run npm run lint, npm test, and npm run build.
  • Cover edge cases: n/a — verify examples against routes.
  • Include the full test output in the PR description.

Example commit message

docs(webhooks): add request examples

Guidelines

  • Minimum 95 percent test coverage for impacted modules.
  • Clear, reviewer-focused documentation.
  • Timeframe: 96 hours.

Community & contribution rewards

  • 💬 Join the TalentTrust community on Discord: https://discord.gg/WqnGpcPx
  • ⭐ This is a GrantFox OSS / Official Campaign task and may be rewarded. When your PR is merged you'll be prompted to rate the project — a 5-star rating is much appreciated.