Skip to content
Before preparing our gym diary project for production, let’s first upload the backend to a cloud service so that our page has access to the data. We chose the Azure service for this book, but the concepts in this chapter can also be applied to other cloud services, such as AWS (https://aws.amazon.com) and GCP (https://cloud.google.com). […]
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, […]
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 […]
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
