NestJS - Interceptors
Why is it important that Exception Mapping Interceptors return observables and do not convert them to promises or other types?
Why is it important that Exception Mapping Interceptors return observables and do not convert them to promises or other types?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand NestJS interceptor expectations
NestJS interceptors work with RxJS observables to handle asynchronous streams.Step 2: Importance of returning observables
Returning observables preserves the reactive pipeline and allows operators like catchError to work properly.Final Answer:
Because NestJS expects interceptors to return observables to maintain reactive flow -> Option DQuick Check:
Interceptors must return observables for reactive flow [OK]
Quick Trick: Return observables in interceptors to keep reactive streams [OK]
Common Mistakes:
- Converting observables to promises inside interceptors
- Assuming promises handle errors better
- Ignoring NestJS reactive design
Master "Interceptors" in NestJS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore NestJS Quizzes