-
Notifications
You must be signed in to change notification settings - Fork 105
[HZG-381] Mutable interceptor #1704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for hardcore-allen-f5257d ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks!
@@ -247,6 +247,8 @@ Map interceptors are chained, so adding the same interceptor to the same map mor | |||
When you add the interceptor in this way, be sure to implement the `hashCode()` method to return the same value for every instance of the interceptor. | |||
It is not strictly necessary, but it is a good idea to also implement `equals()` as this ensures that the map interceptor can be removed reliably. | |||
|
|||
Input values in interceptors are mutable, which means that if you modify the input value in one interceptor, the next interceptor in the chain will receive the updated value. This will also affect any subsequent processing. It's therefore best to avoid modifying the input value directly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also include the reason why we are keeping it mutable?
Added information that the input arguments of the interceptor are mutable.