Skip to content

Add request validation for wallet, community, and resource inputs #1

Description

@Lakes41

The API route schemas currently accept wallet, community, and resource values as basic strings. Add stronger validation so malformed wallet addresses, empty community IDs, and empty resource IDs are rejected before reaching the service layer.

Suggested tasks

  • Add reusable validators for wallet addresses, community IDs, and resource IDs
  • Validate GET /v1/memberships/:wallet
  • Validate GET /v1/members/:wallet
  • Validate POST /v1/access/check
  • Validate GET /v1/communities/:communityId/members
  • Return clear 400 Bad Request responses for invalid inputs
  • Add tests for valid and invalid request payloads

Acceptance criteria

  • Invalid wallet addresses are rejected with a clear error
  • Empty or whitespace-only community and resource values are rejected
  • Validation is covered by route or service tests
  • Existing valid requests continue to work

Metadata

Metadata

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial CampaignCampaign: Official Campaign

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions