-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Rename multipartIterator to parts #147
Conversation
@@ -164,7 +164,12 @@ function fastifyMultipart (fastify, options = {}, done) { | |||
|
|||
fastify.addContentTypeParser('multipart', setMultipart) | |||
fastify.decorateRequest(kMultipartHandler, handleMultipart) | |||
|
|||
fastify.decorateRequest('parts', getMultipartIterator) | |||
// keeping multipartIterator to avoid bumping a major |
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.
wonder if this could be done by using some kind of getter that would be emitting warnings when used. although that might require support on fastify level
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.
maybe just a wrapping function would suffice here, actually
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.
This has been released for so little that I don't think we should bother with a full blown deprecation.
I'm not convinced about a rename at this stage but I'm also not against it. |
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.
LGTM
Checklist
npm run test
andnpm run benchmark
and the Code of conduct