api-fetch: remove redundant next parameter from middleware calls #25001
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
In the middleware API, the `next` function has only one parameter: `options`. The codebase has a few middlewares that call `next( options, next )`, where the second parameter is redundant (although completely harmless). This patch removes these.
jsnajdr added [Type] Code Quality 
Size Change: -1 B Total Size: 1.17 MB
ℹ️ View Unchanged
|
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
In the middleware API, the
nextfunction has only one parameter:options. The codebase has a few middlewares that callnext( options, next ), where the second parameter is redundant (although completely harmless). This patch removes these.