This is good information which I already knew that I could do tests this way. However, most tests have at least 1 service injected into the component and probably many more. If you are writing it the way you said, wouldn't you have to mock out the service each time and then add that to the constructor when instantiating the component. new Component(mockService1, mockService2, etc.) which seems like you would be writing a lot more code using it your way. Shouldn't you keep the beforeEach(() ={}); part (without the async) to do all that code one time since it will need to before run each test anyways. I do get your point as I am having a hard time explaining to fellow developers how this all works.
Given your role as a spokesperson, I strongly recommend investing time in mastering proper breathing techniques. Currently, your delivery often sounds as if you're running out of breath midway through your statements. This issue not only detracts from the topic at hand but also diminishes the overall impact of your communication. Addressing this aspect is critical for maintaining audience engagement and ensuring effective delivery.
Then StackBlits was faster than local environment. But when they introduced webcontainers it is much worser, very often itvdies with out of memory and needs to reinstall every package in this violatile container. So sad
This is the only way I can communicate with your channel. Please kindly enable your comments section. A lot of us want to contribute to your channel but it isn’t helpful as comments are currently disabled. Please kindly enable them. Looking forward to your resolution
@7:24 First Things First, "Organizing for Readability" Is this concept compatible with (abstract base classes) inheritance ? will it fail grossly ? should I avoid inheritance in favor of this concept (I might) ? My concern is: when writing a class based on an abstract base class (and equally, writing an abstract base class in the first place) - some/much of the important/conceptual stuff is defined and visible in the base class, but not at all in the derived class. This greatly disturbs readability, the reader (or I myself) will have to look at 2+ files to get the picture. (I didn't mention how greatly helpful such content is, and went straight to my concern; this is a RU-vid channel and I should probably have asked this on SO instead; but since this feels live, I started right here)
TNice tutorials is my tNice tutorialrd ti watcNice tutorialng tNice tutorials video. I'm switcNice tutorialng over from soft One 4 to soft for my production and your video was the first one I
Around 12:50 the note about the component being injected into the guard is so important (as she said). I recently cleaned up a guard where, despite component being right there in the signature, someone went to the trouble of adding: a touched flag in the global state, and an associated action to dispatch (ngxs) when it should be flipped. Just for this one form. The component is right there.
Very easy to understand, i have been went through all the stack-overflows, and documentations but my concepts was not clear at that time, now thanks to these champs.
What if I want to create components dynamically not from existing components (AComponent, BComponent etc.), but from static HTML files, like it was with ng-include in AngularJS?
Hello. Thanks for the video. What's best practice for using docker and CI? I mean should we install dependencies, compile project in CI and after that wrap dist in docker container or we should do build steps in docker?
7:32 - source map explorer 14:41 - sausage race in milwaukee 17:06 - react change detection (downside of react virtual dom - creates objects which consume memory) 18:31 - angular 2 game plan 19:16 - HTML template - outputs optimized typescript (HTML compiled by Webpack and shipped to the browser) 20:07 - why compile? And not let the browser parse HTML? 1. Syntax errors
It's a shame that Max has to dig the source code and solve a puzzle in order to give this awesome talk, while a bunch of people at Google know every detail of it, but won't do a talk explaining it. -.-
