Skip to content

Pass server interceptor registry to controllers - #237

Open
ydah wants to merge 1 commit into
bigcommerce:mainfrom
ydah:fix/server-interceptor-registry
Open

Pass server interceptor registry to controllers#237
ydah wants to merge 1 commit into
bigcommerce:mainfrom
ydah:fix/server-interceptor-registry

Conversation

@ydah

@ydah ydah commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

What? Why?

Gruf::Server accepts a custom interceptor_registry, and its interceptor management methods update that registry. However, bound services were registered with gRPC as classes, while Controllers::Base always prepared interceptors from the global Gruf.interceptors registry.

As a result, server-specific interceptors were never executed during request handling.

This passes the server's interceptor registry through bound service instances to Controllers::Base, while preserving the global registry as a fallback for controllers instantiated directly.

How was it tested?

  • Added a regression spec for a custom server interceptor registry

@ydah
ydah force-pushed the fix/server-interceptor-registry branch from 8000284 to 0a1e0ae Compare August 9, 2026 23:05
@ydah
ydah force-pushed the fix/server-interceptor-registry branch from 0a1e0ae to 519bb5e Compare August 9, 2026 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant