*ngfor

[sand prawn]

Please read #how-to-get-help

[tender zenith]

i am supposed to get cartitems from username

[sand prawn]

Please, please please, really, read #how-to-get-help . It explains how to use stackblitz to provide a minimal reproduction of your issue. Do that.
Sending walls of code and not telling us what you expect to happen and what happens instead won't allow us to help you.

[tender zenith]

ok i will do stackblitz i thought u meant to provide the details

[tender zenith]

https://stackblitz.com/~/github.com/Junex123/fambruhfinal123 its connected to my database not sure if u can see the product

no you cant

[sand prawn]

Have you read #how-to-get-help ? It doesn't advise you to post all your code as a stackblitz. It advises to post a complete but minimal reproduction of your problem. Eliminate everything that is unrelated to it. Reduce the code to the minimum.

[tender zenith]

https://stackblitz.com/~/github.com/Junex123/problem-cart-productdetail here

first problem ngfor disturbing the html layout and second problem swiper if possible

[sand prawn]

Your code doesn't compile.

[tender zenith]

delete the detail it is database connected

component

cart is also database connected

🐧

service connection errror

[sand prawn]

No. YOU must provide a complete, minimal, correct reproduction.

[tender zenith]

is it updated now

[sand prawn]

OK. So now you have to ask a question. Describe precisely what you're doing, what you expect to happen and what happens instead. Your question is about ngFor, but there is no single instance of ngFor used in your code.

[tender zenith]

it was from database im calling cartitemsbyusername

but when i tried updating the data with cartitems using ngfor the whole html layout is gettting wierd

[sand prawn]

I'm sorry, but I've tried many many times to tell you what to do to make it possible for me to help you, but I failed. So good luck.

[tender zenith]

what detail are you missing

if i add the code i shared here there itll show error compile

[nimble beacon]

Then add it even if it breaks.
The previous point from JBNizet was to ensure the only thing which would break the app would be the isolated problem, not the whole app from not importing it correctly to stackblitz.

Update the stackblitz project with the ngfor part

[tender zenith]

so i have tocreate exact same situationim facing error right now

[nimble beacon]

Yes, update the current project by adding the ngFor to reproduce the error due to it

The point of the repoduction is to allow us to test your situation to understand why it fails.

And, once gain, please mind it's all about your project: the whole html layout is gettting wierd does not mean anything for us. weird might be affecting styles, not displayed, displayed twice, displayed three times, displayed four times, etc. You need to use technical terms.

[tender zenith]

sir check now

*ngFor="let cartItem of cartItems" this we need to use

[nimble beacon]

In which component of your stackblitz project ngFor is used?

[tender zenith]

cartitems

[nimble beacon]

eithery you didn"t save your project, either you used another one.
But there is no ngFor here: https://stackblitz.com/~/github.com/Junex123/problem-cart-productdetail

[tender zenith]

check now

[nimble beacon]

And as your stackblitz porject depends on an APi call from a local databse we do not own, explain directly what's the problem with ngFor:

what's the error?
What's the current behavior?
what's the expected behavior?

[tender zenith]

the html format should remain same i just want to update the details

advice is okay too

[nimble beacon]

I'm close to consider moderation action upon your account if you keep acting like that.
You have pro dev trying to help you on their free time and you act like you do not care to provide the basic context.

It's not even related to Angular or javascript or web dev. You were provided human advices to provide quality questions with #how-to-get-help and you ignore them.

For the last time, that's YOUR project. We can't understand what you do not explain.
ngFor is working fine when used properly: you have problem with it but for the whole discussion, you never shared a single snippet with ngFor.

[tender zenith]

ok ill do it myself