Skip to content
With our micro frontend project ready, we need to prepare it to be consumed by another application. There are several ways to share micro frontends, from the simplest (and obsolete), with the use of iframes, to more modern, but complex, solutions such as module federation. In this section, we will use an approach widely used […]
In the service, we are making HTTP requests to consult exercises and add new ones. For more details about Angular services, you can consult Chapter 5, Angular Services and the Singleton Pattern, and Chapter 9, Exploring Reactivity with RxJS. However, we are experiencing an error because we are not importing the HttpClientModule module. But how […]
To exemplify the use of the micro frontend architecture in our gym diary, we will create a form to define new exercises for our users. Let’s create another Angular project, simulating a new team that will specifically take care of this functionality. In your operating system’s command line, use the following command:ng new gym_exercises –skip-git […]
A big but very true cliché in systems architecture is that there is no silver bullet – that is, there is no one-size-fits-all solution for all problems – and micro frontends cannot escape this cliché. The main advantage of this architecture, before any technical aspect, is its organizational aspect. When we use the micro frontend, […]
As your application grows and becomes more complex, one team alone is not enough to maintain the growth rate, and new people are needed to handle other parts of the application as they appear. At this point, the architecture of your project needs to evolve, and one possibility is to divide your application into several […]
We replaced the previous CSS query with a simpler one that does not depend on layout elements. Use this good practice in your project templates to facilitate E2E testing and make the test less likely to break. We’ll create an E2E test for the new journal entry form, but first, let’s apply the best practice […]
E2E tests aim to evaluate the system from the user’s point of view, simulating operations such as typing in a field, clicking on a button, carrying out the assertion, and evaluating the messages on the screen, just as a user would evaluate whether the action was successful or not. In the Angular ecosystem, in the […]
Angular component unit tests not only examine logic but also assess the values that will be presented on the screen. If your application follows the component architecture recommended by the Angular team (more details in Chapter 4, Components and Pages), you probably won’t have much business logic in your components, delegating it to services. To […]
Terms of Use | About yeagerback | Privacy Policy | Cookies | Accessibility Help | Contact yeagerback
