Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Angular Design Patterns and Best Practices
  • Table Of Contents Toc
  • Feedback & Rating feedback
Angular Design Patterns and Best Practices

Angular Design Patterns and Best Practices

By : Alvaro Camillo Neto
4.4 (14)
close
close
Angular Design Patterns and Best Practices

Angular Design Patterns and Best Practices

4.4 (14)
By: Alvaro Camillo Neto

Overview of this book

Single page applications (SPAs) have become the standard for most web experiences. Angular, with its batteries-included approach, has emerged as a powerful framework for simplifying the development of these interfaces by offering a comprehensive toolbox. This book guides you through the Angular ecosystem, uncovering invaluable design patterns and harnessing its essential features. The book begins by laying a strong foundation, helping you understand when and why Angular should be your web development framework of choice. The next set of chapters will help you gain expertise in component design and architecting efficient, flexible, and high-performing communication patterns between components. You’ll then delve into Angular's advanced features to create forms in a productive and secure way with robust data model typing. You'll also learn how to enhance productivity using interceptors to reuse code for common functionalities, such as token management, across various apps. The book also covers micro frontend architecture in depth to effectively apply this architectural approach and concludes by helping you master the art of crafting tests and handling errors effortlessly. By the end of this book, you'll have unlocked the full potential of the Angular framework.
Table of Contents (19 chapters)
close
close
1
Part 1: Reinforcing the Foundations
7
Part 2: Leveraging Angular’s Capabilities
12
Part 3: Architecture and Deployment

Updating your project with the Angular CLI

The Angular framework is continually evolving with new features and optimizations, but to help communities and developers keep organized and their applications up to date, the Angular team uses semantic versioning to number their releases.

A semantic version number is composed of three parts and each part has the following representation:

  • Major: A number that is increased every time there is a change in the framework, which in turn requires us to change something in our application so that it continues to work, also known as a breaking change
  • Minor: A number that is increased when the new version has a new functionality that we can use, but if we don’t use it, we don’t need to change our application
  • Patch: A number that is increased when there is a correction to the framework and we do not need to change our code; this is widely used for versions that have security corrections

In this book, we are working...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY