Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: add a new page for advanced topics #2481

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

Open
jmcdo29 wants to merge 4 commits into nestjs:master
base: master
Choose a base branch
Loading
from jmcdo29:feat/advanced-nestjs

Conversation

Copy link
Member

@jmcdo29 jmcdo29 commented Oct 1, 2022

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Docs
  • Other... Please describe:

What is the current behavior?

There's no deep dive/advanced docs that could help some people understand why things are the way they are.

What is the new behavior?

There's a new page that discusses how @Injectable() works and what it's really doing.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

tonivj5 and bacebu4 reacted with thumbs up emoji micalevisk, tonivj5, and bacebu4 reacted with heart emoji
Currently only discusses how `@Injectable()` works. We can add more in
as time goes.
Copy link

I appreciate this MR. I was trying to figure out in my own code how Nest.js was injecting into my class when I had accidentally omitted the "Injectable" decorator. I found my answer here, "by technicality [having @Inject on a contructor param] does enough to make TypeScript emit all the same metadata".

jmcdo29 and micalevisk reacted with thumbs up emoji

I started using Helix as an editor which doesn't directly support
soft line wraps (it does now but it didn't) and got in the habit of
keeping my markdown files to around 80 characters per line. This also
leads to easier times in code reviews finding incorrect words and
highlighting them due to only a single line being highlighted instead
of an entire paragraph
Copy link
Contributor

Tony133 commented Jul 19, 2023

Hi @jmcdo29, 👋🏻

I read the article you wrote on Trilon's blog: https://trilon.io/blog/nestjs-metadata-deep-dive 🔥, very interesting! Great!
While reading this article, this PR came to my mind, do you think we can merge this PR or do you still need to add something?
I think it is very useful to add it to the NestJS documentation.

@kamilmysliwiec when you find some time can you take a look at it so we can see if we can add it to the documentation ?

Copy link
Member

micalevisk commented Dec 16, 2023
edited
Loading

I wonder if 'internal' instead of 'advanced' would be better 🤔

because we can have advanced stuff for user-facing concepts

Reviewers
3 more reviewers

@carnesen carnesen carnesen left review comments

@micalevisk micalevisk micalevisk approved these changes

@Tony133 Tony133 Tony133 approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /