ok mind blown, i am all for this! please let me kow when you upload it i am going to purchase. i see so many use cases here for myself, great info and intro to this man!
Just uploaded it - there was a technical issue on lemon squeezy which is resolved now :) Glad you liked the store - I love refactoring stuff - so enjoyed this process!
@@ZoaibKhan i just bought it to play around with it. I wish you had a shared githib private repo that all your pateron supporters could collaborate on. i think that would be awesome. thanks buddy!
Well, you can create a separate component and route for login - and then keep the rest of the dashboard + menu routes in a separate set of routes. There will be a router outlet on the main app component - and then there is already a router outlet for the normal page routes but it'll be nested inside the container Hope that helps a bit! If not, this seems like a good thing to show on video :)
ok mind blown, i am all for this! please let me kow when you upload it i am going to purchase. i see so many use cases here for myself, great info and intro to this man!
Just uploaded it - there was a technical issue on lemon squeezy which is resolved now :)
Glad you liked the store - I love refactoring stuff - so enjoyed this process!
@@ZoaibKhan i just bought it to play around with it. I wish you had a shared githib private repo that all your pateron supporters could collaborate on. i think that would be awesome. thanks buddy!
Could you please make a tutorial about local firestore emulator with angular?
hello zoaib how add download progress bar in angular with fetch api ?
Thanks for the lesson! This is a really useful tool.
What about signalStore and Resource API interaction?
I think we might see some built in way to define resources within the signal store in future versions on the pattern of with computed.
Thanks for the video.
What Can I do to render my login page outside this dashboard. I need a help, please!
Well, you can create a separate component and route for login - and then keep the rest of the dashboard + menu routes in a separate set of routes. There will be a router outlet on the main app component - and then there is already a router outlet for the normal page routes but it'll be nested inside the container
Hope that helps a bit! If not, this seems like a good thing to show on video :)
@@ZoaibKhan Your explanation is very clear. I thank you once again. I will implement it to see if I can be successful.
can you share the Sourcecode ?
It's part of the dashboard - the complete code can be bought on the link in the description.