Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

getType() in ExecutionContext and ArgumentsHost

See original GitHub issue

I’m submitting a…


[ ] Regression 
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request (new chapter/page)
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Expected behavior

Ref https://github.com/nestjs/nest/issues/1581

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment


For Tooling issues:
- Node version: XX  
- Platform:  

Others:

Issue Analytics

State:
Created 4 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

johnbiundocommented, Sep 24, 2019

I’m proposing a new (small) chapter on writing universal guards and interceptors based on the topic in https://github.com/nestjs/nest/issues/1581, and this new (getType()) feature. At the same time, I’m proposing that we simplify the discussion of ArgumentsHost / ExecutionContext in the chapters where it’s introduced (Exception Filters, Guards, Interceptors), as these seem to trip people up and introduce concepts that aren’t necessarily relevant when someone is first learning Nest. (And in the spirit that the Overview chapters essentially assume that the user is building in the HTTP context).

I’ve already submitted one PR (which was just pushed today) to simplify Exception Filters handling of this topic. I’m going to submit similar revisions for Guards and Interceptors shortly.

Where I could use some help from people like @dantman, @hexonaut, or anyone else who has an interest in this, is a simple use-case description, and basic sample code (tutorial-like), for using getType() to write universal components. If you have input on this topic, please reply to this issue. Thanks!

0reactions

kamilmysliwieccommented, Jan 28, 2020

Tracking here https://github.com/nestjs/docs.nestjs.com/pull/954

Top Results From Across the Web

Execution context | NestJS - A progressive Node.js framework

These utilities provide information about the current execution context which can be used to build ... Do this with the getType() method of...

NESTJS Get the execution context within the exception filter

So I found that identification data are in the execution context only for a ... ArgumentsHost): Record<string, unknown> { switch (host.

ExecutionContext | @nestjs/microservices

Returns a reference to the handler (method) that will be invoked next in the request pipeline. Returns Function. getType. getType<TContext>(): TContext.

@nestjs/common ExecutionContext TypeScript Examples

getType() === 'http') { // http request const httpContext = context.switchToHttp(); request = httpContext.getRequest(); response = httpContext.

get_type - Code Search

packages/common/interfaces/features/arguments-host.interface.ts ... current execution context type (string); */; getType<TContext extends ...