@greptileai

Greptile Summary

Adds a ContentType() convenience method to all ClientWithResponses response types that returns the Content-Type response header, generated by default with an opt-out via the new skip-client-response-content-type config flag. The implementation (template, Go struct, JSON schema) is internally consistent and the generated code is correct.

• The opt-out default differs from the analogous Bytes() method (introduced in feat(client): Add Bytes() to ClientWithResponses responses #1780), which is opt-in. The PR description claims "a similar approach as feat(client): Add Bytes() to ClientWithResponses responses #1780" but the actual behavior is opposite, creating an API surface inconsistency and risking compilation breakage for users who have already defined their own ContentType() on a generated type.
• There is no dedicated integration test (analogous to internal/test/issues/issue240/) to validate the method's behavior or confirm the skip option suppresses it.

Confidence Score: 4/5

Safe to merge with minor concerns; the implementation is correct but the opt-out default is inconsistent with Bytes() and there is no dedicated test.

All findings are P2 — design inconsistency between opt-out ContentType() and opt-in Bytes(), and missing integration test. No correctness defects were found. The design inconsistency has a concrete risk (duplicate-method compilation failure for users who have hand-written a ContentType() method on a generated type), warranting a slight reduction from 5/5.

pkg/codegen/templates/client-with-responses.tmpl — the opt-out design choice should be confirmed intentional, and a dedicated test should be added.

_{Reviews (1): Last reviewed commit: "Make ContentType() default on" | Re-trigger Greptile}