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
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
GET /v1/memberships/:walletGET /v1/members/:walletPOST /v1/access/checkGET /v1/communities/:communityId/members400 Bad Requestresponses for invalid inputsAcceptance criteria