Validate retry configuration values

[grantfox-oss]

Summary

Validate retry configuration at client construction or request time so invalid values do not cause surprising delays, infinite loops, or silent retry failures.

Current Behaviour

RetryConfig accepts optional values such as maxRetries, baseDelayMs, maxDelayMs, and retryableStatuses, but the config validation only checks apiUrl and timeoutMs.

Expected Behaviour

Invalid retry settings should throw a clear GuildPassError before requests are made.

Suggested Implementation

Add retry config validation to validateConfig for global retry settings and to HttpClient for per-request retry overrides. Reject negative retry counts, negative delays, empty or invalid status lists, and non-finite numeric values.

Files or Areas Likely Affected

• src/config/sdkConfig.ts
• src/http/httpClient.ts
• src/http/http.types.ts
• src/errors/errorCodes.ts
• tests/client.test.ts
• tests/httpClient.test.ts

Acceptance Criteria

• Negative maxRetries values are rejected
• Negative or non-finite delay values are rejected
• maxDelayMs lower than baseDelayMs is handled intentionally or rejected
• Invalid retry status codes are rejected
• Per-request retry overrides are validated
• Error messages identify the invalid retry field

Additional Notes

Assumption: failing fast is preferred over trying to correct malformed retry settings silently.

[Marvy247]

Hi Maintainer, I've reviewed the issue description, and I'm confident I can implement all the requested details smoothly.​ Please assign this issue to me! I can have a PR ready for review in a few hours.
Thank You.

[zeke-codes]

Hi maintainer, can i handle this issue?

[femiolutayo]

I'm applying for this issue because I enjoy improving software reliability and preventing configuration-related bugs before they reach production. This task aligns with my experience in validation, testing, and writing robust code that fails fast with clear error messages.

[Babigdk]

I'd like to work on this issue. I will extend retry configuration validation in both validateConfig and HttpClient to fail fast on invalid retry settings, including negative or non-finite values, invalid status codes, and inconsistent delay configurations.

The implementation will ensure both global and per-request retry options are validated, provide clear field-specific error messages, and include test coverage for all acceptance criteria.

[morelucks]

Hello,

This issue aligns well with my experience as a Web3 builder. I’ve worked on Celo-based applications with a focus on usability, smart contracts, stablecoin payments, and real-world adoption.

I also have contribution experience through OnlyDust, Drips Waves 1–5, and the GrantFox beta campaign. I’m confident I can deliver a clean and well-tested solution within 24 hours.

I’d be excited to contribute to this.

[grantfox-oss]

🦊 GrantFox — @femiolutayo has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #57)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.