Greptile Summary

This PR implements per-operation middleware support for both Echo v4 and Echo v5 backends by introducing RegisterHandlersWithOptions (with a RegisterHandlersOptions struct containing BaseURL and OperationMiddlewares) and refactoring the existing RegisterHandlers/RegisterHandlersWithBaseURL helpers to delegate to it. The change is backward-compatible, correctly uses the raw spec operationId as the map key (with a normalized-identifier fallback when the spec omits one), and includes a solid regression test in internal/test/issues/issue-518/.

• examples/petstore-expanded/echo/api/petstore-server.gen.go contains unrelated parameter-binding changes (BindQueryParameter → BindQueryParameterWithOptions with added Type/Format fields; same for BindStyledParameterWithOptions) that do not appear in the echo-v5 equivalent — this file appears to have been regenerated with a toolchain that includes additional unreleased changes, and will likely cause a CI diff failure.

Confidence Score: 3/5

Mostly safe to merge, but the unrelated binding-change drift in the echo/v4 petstore example file needs to be resolved first.

The core template change and regression test are well-implemented, but a P1 finding — unrelated parameter-binding changes in examples/petstore-expanded/echo/api/petstore-server.gen.go absent from the echo-v5 counterpart — indicates the file was regenerated with a different toolchain and will likely cause a CI make generate diff failure.

examples/petstore-expanded/echo/api/petstore-server.gen.go — contains binding-call changes unrelated to this PR that are not present in the echo-v5 equivalent.

_{Reviews (1): Last reviewed commit: "per-operation middleware in Echo" | Re-trigger Greptile}

Greptile Summary

This PR implements per-operation middleware support for both Echo v4 and Echo v5 backends by introducing RegisterHandlersWithOptions (with a RegisterHandlersOptions struct containing BaseURL and OperationMiddlewares) and refactoring the existing RegisterHandlers/RegisterHandlersWithBaseURL helpers to delegate to it. The change is backward-compatible, correctly uses the raw spec operationId as the map key (with a normalized-identifier fallback when the spec omits one), and includes a solid regression test in internal/test/issues/issue-518/.

* `examples/petstore-expanded/echo/api/petstore-server.gen.go` contains unrelated parameter-binding changes (`BindQueryParameter` → `BindQueryParameterWithOptions` with added `Type`/`Format` fields; same for `BindStyledParameterWithOptions`) that do not appear in the echo-v5 equivalent — this file appears to have been regenerated with a toolchain that includes additional unreleased changes, and will likely cause a CI diff failure.

Confidence Score: 3/5

Mostly safe to merge, but the unrelated binding-change drift in the echo/v4 petstore example file needs to be resolved first.

The core template change and regression test are well-implemented, but a P1 finding — unrelated parameter-binding changes in examples/petstore-expanded/echo/api/petstore-server.gen.go absent from the echo-v5 counterpart — indicates the file was regenerated with a different toolchain and will likely cause a CI make generate diff failure.

examples/petstore-expanded/echo/api/petstore-server.gen.go — contains binding-call changes unrelated to this PR that are not present in the echo-v5 equivalent.

Important Files Changed

Comments Outside Diff (1)

1. `examples/petstore-expanded/echo/api/petstore-server.gen.go`, line 63-73 ([link](https://github.com/oapi-codegen/oapi-codegen/blob/f4a74a25e165303380af81ef55b6f54d17b8c948/examples/petstore-expanded/echo/api/petstore-server.gen.go#L63-L73))
   [![P1](https://camo.githubusercontent.com/4e5a362f3ef5d2d58ede5ed80de15a55078df1b6f7dec5850902b2cf5bce3eb8/68747470733a2f2f6772657074696c652d7374617469632d6173736574732e73332e616d617a6f6e6177732e636f6d2f6261646765732f70312e7376673f763d37)](#) **Unrelated drift in regenerated file**
   `examples/petstore-expanded/echo/api/petstore-server.gen.go` contains parameter-binding changes unrelated to this PR's stated goal of per-operation middleware. Specifically, calls to `BindQueryParameter` have been replaced with `BindQueryParameterWithOptions` (gaining `Type`/`Format` fields), and `BindStyledParameterWithOptions` call sites gain the same extra fields. These changes do not appear in the otherwise-analogous echo-v5 petstore file, suggesting this file was regenerated with a local toolchain that includes additional unreleased changes. Per the project policy, CI fails when `make generate` produces a diff — if the intended generator does not yet emit these binding changes, CI will fail on this file.

Reviews (1): Last reviewed commit: "per-operation middleware in Echo" | Re-trigger Greptile

@greptileai - this is because for some reason, the petstore boilerplate hasn't successfully regenerated into a while. Our "make generate" target bypasses it. I will fix that in a separate commit. This is correct.

Got it, thanks for the context. If the petstore example is intentionally excluded from make generate and will be fixed separately, the drift is expected and not a blocker for this PR.

Tip: You can give me more context with .greptile/rules.md so I get this right next time.