Question 1

How to add retry logic with gentleman?

Accepted Answer

Use the gentleman-retry plugin, which provides configurable retry policies. Install it separately, then attach it to your client or request via the Use() method, similar to other plugins shown in examples.

Question 2

Gentleman vs resty: which is better for Go HTTP clients?

Accepted Answer

Gentleman focuses on extensibility and middleware composition, ideal for custom API clients. Resty offers more built-in features out-of-the-box but is less plugin-driven. Choose Gentleman if you need fine-grained control and reuse.

Question 3

How to mock HTTP requests for testing with gentleman?

Accepted Answer

Integrate the gentleman-mock plugin, which uses gock under the hood. It allows you to define mock responses and verify requests, making end-to-end testing easier, as referenced in the README.

Question 4

Is gentleman good for building REST API clients?

Accepted Answer

Yes, it's well-suited for domain-specific REST API clients due to its plugin architecture and helpers for JSON/XML serialization. The inheritance model helps reuse common logic across endpoints.

Question 5

How to handle authentication with gentleman plugins?

Accepted Answer

Use the built-in auth plugin to set authorization headers, or create custom plugins for complex auth flows. Plugins can intercept requests to add tokens dynamically, leveraging the middleware phases.

Question 6

What are the middleware phases in gentleman?

Accepted Answer

Gentleman supports phases like request, response, error, and intercept, allowing logic execution at different HTTP lifecycle stages. This enables tasks like logging, error handling, and request modification before sending.

gentleman

What is gentleman?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions