Can you use a FileInterceptor with a TransformPipe
I've met an issue with the TransformPipe - it works as long, as I don't use the FileInterceptor. Since I need both functionalities it confused me. I've created an issue on Github, but Kamil wrote on it, that it is a normal framework behavior. Nor I, nor my friends, didn't find any references to this "normal" behavior in the official documentation. Do you have any ideas?
Code is here:
Controller
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file) {
return file
}
Pipe
@Injectable()
export class SamplePipe implements PipeTransform {
transform(value: any, metadata: ArgumentMetadata) {
console.log("I'm working")
return value;
}
}
javascript node.js typescript nestjs
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
asked Nov 16 '18 at 11:49
hypeofpipe
507
add a comment |
I've met an issue with the TransformPipe - it works as long, as I don't use the FileInterceptor. Since I need both functionalities it confused me. I've created an issue on Github, but Kamil wrote on it, that it is a normal framework behavior. Nor I, nor my friends, didn't find any references to this "normal" behavior in the official documentation. Do you have any ideas?
Code is here:
Controller
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file) {
return file
}
Pipe
@Injectable()
export class SamplePipe implements PipeTransform {
transform(value: any, metadata: ArgumentMetadata) {
console.log("I'm working")
return value;
}
}
javascript node.js typescript nestjs
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
asked Nov 16 '18 at 11:49
hypeofpipe
507
add a comment |
I've met an issue with the TransformPipe - it works as long, as I don't use the FileInterceptor. Since I need both functionalities it confused me. I've created an issue on Github, but Kamil wrote on it, that it is a normal framework behavior. Nor I, nor my friends, didn't find any references to this "normal" behavior in the official documentation. Do you have any ideas?
Code is here:
Controller
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file) {
return file
}
Pipe
@Injectable()
export class SamplePipe implements PipeTransform {
transform(value: any, metadata: ArgumentMetadata) {
console.log("I'm working")
return value;
}
}
javascript node.js typescript nestjs
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
asked Nov 16 '18 at 11:49
hypeofpipe
507
I've met an issue with the TransformPipe - it works as long, as I don't use the FileInterceptor. Since I need both functionalities it confused me. I've created an issue on Github, but Kamil wrote on it, that it is a normal framework behavior. Nor I, nor my friends, didn't find any references to this "normal" behavior in the official documentation. Do you have any ideas?
Code is here:
Controller
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file) {
return file
}
Pipe
@Injectable()
export class SamplePipe implements PipeTransform {
transform(value: any, metadata: ArgumentMetadata) {
console.log("I'm working")
return value;
}
}
javascript node.js typescript nestjs
javascript node.js typescript nestjs
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
asked Nov 16 '18 at 11:49
hypeofpipe
507
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
asked Nov 16 '18 at 11:49
hypeofpipe
507
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
edited Nov 16 '18 at 16:50
chazsolo
5,1071233
5,1071233
asked Nov 16 '18 at 11:49
hypeofpipe
507
asked Nov 16 '18 at 11:49
hypeofpipe
507
asked Nov 16 '18 at 11:49
hypeofpipe
507
507
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Pipes only work as the following types: 'body' | 'query' | 'param' | 'custom' corresponding to @Body(), @Query(), @Param() or custom decorators like @User(). In your example you don't have any of these and that's why the pipe is not applied.
So if you add one of these to your example, the pipe will be applied (in this case to @Body()).
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file, @Body() body) {
^^^^^^^^^^^^^
return file
}
If you use @UsePipes() the pipe will be applied everywhere where applicable. You can also use @Body(SimplePipe) body to only apply the pipe to the body.
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
I think you've misunderstood the difference between controller-scope pipes and argument-scope ones.
– hypeofpipe
Nov 16 '18 at 17:30
I'm assuming your referring to my last paragraph? If you for example have multiple@Params in your route, then@UsePipesis applied to all of them, whereas argument-scope ones only apply to one@Param. I don't see where there is a mistake, can you clarify?
– Kim Kern
Nov 16 '18 at 17:38
Pipes are however never applied to the route itself but only its arguments. If you wanted to apply it to the whole route you'd use an Interceptor instead.
– Kim Kern
Nov 16 '18 at 17:44
Wow, thank you, I'll check it
– hypeofpipe
Nov 16 '18 at 19:40
@hypeofpipe Did it work for you now? :-)
– Kim Kern
Dec 11 '18 at 22:02
|
show 1 more comment
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337293%2fcan-you-use-a-fileinterceptor-with-a-transformpipe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Pipes only work as the following types: 'body' | 'query' | 'param' | 'custom' corresponding to @Body(), @Query(), @Param() or custom decorators like @User(). In your example you don't have any of these and that's why the pipe is not applied.
So if you add one of these to your example, the pipe will be applied (in this case to @Body()).
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file, @Body() body) {
^^^^^^^^^^^^^
return file
}
If you use @UsePipes() the pipe will be applied everywhere where applicable. You can also use @Body(SimplePipe) body to only apply the pipe to the body.
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
I think you've misunderstood the difference between controller-scope pipes and argument-scope ones.
– hypeofpipe
Nov 16 '18 at 17:30
I'm assuming your referring to my last paragraph? If you for example have multiple@Params in your route, then@UsePipesis applied to all of them, whereas argument-scope ones only apply to one@Param. I don't see where there is a mistake, can you clarify?
– Kim Kern
Nov 16 '18 at 17:38
Pipes are however never applied to the route itself but only its arguments. If you wanted to apply it to the whole route you'd use an Interceptor instead.
– Kim Kern
Nov 16 '18 at 17:44
Wow, thank you, I'll check it
– hypeofpipe
Nov 16 '18 at 19:40
@hypeofpipe Did it work for you now? :-)
– Kim Kern
Dec 11 '18 at 22:02
|
show 1 more comment
Pipes only work as the following types: 'body' | 'query' | 'param' | 'custom' corresponding to @Body(), @Query(), @Param() or custom decorators like @User(). In your example you don't have any of these and that's why the pipe is not applied.
So if you add one of these to your example, the pipe will be applied (in this case to @Body()).
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file, @Body() body) {
^^^^^^^^^^^^^
return file
}
If you use @UsePipes() the pipe will be applied everywhere where applicable. You can also use @Body(SimplePipe) body to only apply the pipe to the body.
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
I think you've misunderstood the difference between controller-scope pipes and argument-scope ones.
– hypeofpipe
Nov 16 '18 at 17:30
I'm assuming your referring to my last paragraph? If you for example have multiple@Params in your route, then@UsePipesis applied to all of them, whereas argument-scope ones only apply to one@Param. I don't see where there is a mistake, can you clarify?
– Kim Kern
Nov 16 '18 at 17:38
Pipes are however never applied to the route itself but only its arguments. If you wanted to apply it to the whole route you'd use an Interceptor instead.
– Kim Kern
Nov 16 '18 at 17:44
Wow, thank you, I'll check it
– hypeofpipe
Nov 16 '18 at 19:40
@hypeofpipe Did it work for you now? :-)
– Kim Kern
Dec 11 '18 at 22:02
|
show 1 more comment
Pipes only work as the following types: 'body' | 'query' | 'param' | 'custom' corresponding to @Body(), @Query(), @Param() or custom decorators like @User(). In your example you don't have any of these and that's why the pipe is not applied.
So if you add one of these to your example, the pipe will be applied (in this case to @Body()).
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file, @Body() body) {
^^^^^^^^^^^^^
return file
}
If you use @UsePipes() the pipe will be applied everywhere where applicable. You can also use @Body(SimplePipe) body to only apply the pipe to the body.
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
Pipes only work as the following types: 'body' | 'query' | 'param' | 'custom' corresponding to @Body(), @Query(), @Param() or custom decorators like @User(). In your example you don't have any of these and that's why the pipe is not applied.
So if you add one of these to your example, the pipe will be applied (in this case to @Body()).
@UsePipes(SamplePipe)
@UseInterceptors(FileInterceptor('file'))
@Post()
samplePost(@UploadedFile() file, @Body() body) {
^^^^^^^^^^^^^
return file
}
If you use @UsePipes() the pipe will be applied everywhere where applicable. You can also use @Body(SimplePipe) body to only apply the pipe to the body.
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
edited 2 days ago
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
answered Nov 16 '18 at 16:00
Kim Kern
7,46422344
7,46422344
I think you've misunderstood the difference between controller-scope pipes and argument-scope ones.
– hypeofpipe
Nov 16 '18 at 17:30
I'm assuming your referring to my last paragraph? If you for example have multiple@Params in your route, then@UsePipesis applied to all of them, whereas argument-scope ones only apply to one@Param. I don't see where there is a mistake, can you clarify?
– Kim Kern
Nov 16 '18 at 17:38
Pipes are however never applied to the route itself but only its arguments. If you wanted to apply it to the whole route you'd use an Interceptor instead.
– Kim Kern
Nov 16 '18 at 17:44
Wow, thank you, I'll check it
– hypeofpipe
Nov 16 '18 at 19:40
@hypeofpipe Did it work for you now? :-)
– Kim Kern
Dec 11 '18 at 22:02
|
show 1 more comment
I think you've misunderstood the difference between controller-scope pipes and argument-scope ones.
– hypeofpipe
Nov 16 '18 at 17:30
I'm assuming your referring to my last paragraph? If you for example have multiple@Params in your route, then@UsePipesis applied to all of them, whereas argument-scope ones only apply to one@Param. I don't see where there is a mistake, can you clarify?
– Kim Kern
Nov 16 '18 at 17:38
Pipes are however never applied to the route itself but only its arguments. If you wanted to apply it to the whole route you'd use an Interceptor instead.
– Kim Kern
Nov 16 '18 at 17:44
Wow, thank you, I'll check it
– hypeofpipe
Nov 16 '18 at 19:40
@hypeofpipe Did it work for you now? :-)
– Kim Kern
Dec 11 '18 at 22:02
I think you've misunderstood the difference between controller-scope pipes and argument-scope ones.
– hypeofpipe
Nov 16 '18 at 17:30
I think you've misunderstood the difference between controller-scope pipes and argument-scope ones.
– hypeofpipe
Nov 16 '18 at 17:30
I'm assuming your referring to my last paragraph? If you for example have multiple
@Params in your route, then @UsePipes is applied to all of them, whereas argument-scope ones only apply to one @Param. I don't see where there is a mistake, can you clarify?– Kim Kern
Nov 16 '18 at 17:38
I'm assuming your referring to my last paragraph? If you for example have multiple
@Params in your route, then @UsePipes is applied to all of them, whereas argument-scope ones only apply to one @Param. I don't see where there is a mistake, can you clarify?– Kim Kern
Nov 16 '18 at 17:38
Pipes are however never applied to the route itself but only its arguments. If you wanted to apply it to the whole route you'd use an Interceptor instead.
– Kim Kern
Nov 16 '18 at 17:44
Pipes are however never applied to the route itself but only its arguments. If you wanted to apply it to the whole route you'd use an Interceptor instead.
– Kim Kern
Nov 16 '18 at 17:44
Wow, thank you, I'll check it
– hypeofpipe
Nov 16 '18 at 19:40
Wow, thank you, I'll check it
– hypeofpipe
Nov 16 '18 at 19:40
@hypeofpipe Did it work for you now? :-)
– Kim Kern
Dec 11 '18 at 22:02
@hypeofpipe Did it work for you now? :-)
– Kim Kern
Dec 11 '18 at 22:02
|
show 1 more comment
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337293%2fcan-you-use-a-fileinterceptor-with-a-transformpipe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
