Комментарии:
Thank you Beau!
I really enjoyed making this course, I hope that it will be helpful to anyone who wants to learn about NestJs! 😊
Why don't you add the dubbing feature to Arabic?!!!
ОтветитьWhat's the point of the config module if I can access process.env.VAR globally? I looked through the docs lightly, and the only benefit I could think of is caching, and when you want to use different envPaths. Even then, I have trouble understanding the benefit of envPaths because it says a variable takes on the first value it finds. That would mean that across different env files I would have to set a prefix to my env vars like DEV_ or QA_, which kind of defeats the purpose of the env files. What I mean by this is that the VAR_NAME should be the same across all files, just the value should change depending on environment. Maybe I misunderstood this? Thank you! Amazing video so far.
ОтветитьSo you're telling me that when I instantiate ValidationPipe with useGlobalPipes, it knows we have used class validator decorators within the Dto class automatically? Is this through type recognition in the route callback @Body() dto: AuthDto? Can you speak a little bit more on how this works? I'm not super familiar with proper backend design.
Ответить9 minutes in and ready to take this long journey. I'll report back at the end!
Ответитьworst explanation , he writes code and remove it
first prepare you roadmap , explain why we do this with a brief example ,
when you copy something explain why we need it briefly don't just hardcode everything
as a beginners you are making everything harder
STOP EXPLAINING
I am facing problem when creating docker-compose file, it come out just plain file without anything in it. Am also can't auto generate a module using nest g module nameModule because something was disable ? Can someone help me
ОтветитьThis tutorial has been amazing. Everythings been clearly explained at a not too fast not too slow pace and your accent is cool too!
ОтветитьIn get me api, why don't we creating user.service.js file to handle finding user logic but implement it in jwt.strategy.ts file? thank you very munch for this course and your answer
ОтветитьI was thinking you will wrte the code completely before the end to end testing. Now, I am not sure how I can follow through to the end...😭
ОтветитьInstead of using withHeader() to insert the bearer token in Pactum you could use the method withBearerToken() and provide the name from the stores, ie: ".withBearerToken('$S{userToken}')"
ОтветитьWhat extension you use to have this icons?
Ответитьhow did th first route became /auth/signup if we wrote path as /signup only??
ОтветитьI have watched and also coded with tutors like 400 tutorials till today (I am counting the number =)) but this tutorial was one of the best tutorials I have ever watched by so far. Very neat, crystal, no questions in my mind, nothing like "tutor does something but you fail with the same code", very helpful. Thanks god there are streamers like Vlad!
ОтветитьVery good one. I like when explain each small thing simply
ОтветитьHi thanks for wonderful tutorials. I'm working on the signup logic session and got suck in this problems. When I tried to post the user, the error said that my public.user table does not exist in the database. Do you have any ideas how to fix this? Thanks again
ОтветитьI think it would be really helpfull to explain a bit more the Imsonia / Postman aspects. or mention them, bc I got stuck in a couple of moments. because I didn't notice that x field was different (POST from GET) or where to put the variables.
Great tutorial anyhow !!
Great course!! (I'm in the middle of it right now)
The thing I dont get, is why do we need to import everything multiple times.
We create a prisma service. We import it in prisma module. We import the prisma module with that service into auth module. We import the prisma service into the auth module's service. Also, we need to additionally allow importing the service in another service.. I get feel that we importing everything at least twice...
Good work
ОтветитьThanks for the guide! I learn Nest and this course is good for understanding and first experience
ОтветитьI'm doing eveything as shown in the videp, except for Docker. I don't have enough RAM for that.
ОтветитьI'm having some difficulties with the testing commands you made for the e2e section. individually each command works fine but if I try to use either the db:test:restart or db:dev:restart it tells me it can't find my localhost:<assigned port>. as I mentioned the prisma:<test/dev>:deploy, db:<test/dev>:rm, and the db:<test/dev>:up commands all work if I initialize them individually. Has anyone else come across this? I'm able to do the testing but not automate the commands the same way you have in your example.
ОтветитьOne of the best courses from Free Code Camp!!
ОтветитьSome heads up fellow learners, I faced some issue: if you face issues, after changes to your schema, use npx prisma dev push, use import { Prisma } from "@prisma/client"; error instanceof Prisma.PrismaClientKnownRequestError for caching the error code.
Great course.
My code was working very fine until I added the following in the package.json file as the video directed;
"prisma:dev:deploy": "prisma migrate deploy",
"db:dev:rm": "docker-compose rm dev-db -s -f -v",
"db:dev:up": "docker-compose up dev-db -d",
"db:dev:restart": "npm run db:dev:rm && npm run db:dev:up && sleep 1 && npm run prisma:dev:deploy"
The error I am having is Error: P1001: Can't reach database server at `localhost`:`5434`
Please make sure your database server is running at `localhost`:`5434`
How do I overcome this problem?
I just switched from Rust/Axum to TS/NestJS. The developer experience with TS and NestJS is hands down beautiful.
Ответитьwhat tool to have color terminal like admin in video
Ответитьimport { Module } from '@nestjs/common'; 201.6k (gzipped: 42.3k)
@Module({
imports: [AuthModule],
})
export class AuthModule{}
I am getting this error
Followed and enjoyed every bit of this lesson! My journey to fullstack development starts here! Thank you!
ОтветитьI own you 35 % of my salary lol
ОтветитьCan you do a video with TypeOrm one more?
Ответитьthanks for the tutorial! anyone know any tutorials covers how you can test guards/decorators/interceptors, as its own standalone test or integrated with one of the e2e tests? been having a hard time finding these tutorials!
Ответитьit's bit late but i have one question, during e-2-e test npm run test:e2e it's giv me an error because the command first remove docker container testdb but it's not available how it will be resolve
ОтветитьThanks so much for this. I learnt a lot.
I notice on certain lines he uses await e.g on delete await this.prisma.bookmark.delete({...})
But not on update e.g return this.prisma.bookmark.update({...})
Can one use await when updating e.g const newBookmark = await this.prisma.bookmark.update({...}) ?
Assuming it's usually good practice to wait for the action to finish.
非常棒的课程,学习了。
ОтветитьAmazing Course. Fantastic teaching way!
ОтветитьDope master class.
ОтветитьYou are an amazing teacher! Thank you so muuuuch!!!
ОтветитьSo I am confused about something, We are using NestJs with basically SQL running in docker? I am new to this btw
ОтветитьNice tutorial I am glad to find this, thank you sir, just one concern regarding Prisma cleanDb seems pretty risky
ОтветитьThank you so much for such a valuable tutorial <3
Ответить