WW-5586 fix(core): enable WithLazyParams interceptor configuration in stacks #1414
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Summary
Fixes WW-5586 - Enable
WithLazyParamsinterceptors to be configured via interceptor stack parameters.Problem
Previously, interceptors implementing
WithLazyParamscould not be configured through interceptor stack parameter syntax becauseDefaultInterceptorFactoryskipped property setting entirely for these interceptors. This prevented configurations like:Solution
Modified
DefaultInterceptorFactoryto always set properties during interceptor creation, regardless ofWithLazyParamsinterface implementation. Expression parameters (containing${...}) are re-evaluated at invocation time viaLazyParamInjector, while static parameters remain unchanged.Changes
WithLazyParamsinterceptorstestInvokeWithLazyParamsStackConfiguration()to verify both static and expression parameters work in stacksTesting
DefaultActionInvocationTestpassBenefits
This unblocks WW-5585 and enables combining static security constraints with dynamic expressions in the same interceptor stack reference.
🤖 Generated with Claude Code