Updating typo to stable version
The code that we end this article with is tagged as part-6. To support a thriving ecosystem, Angular needs to be both stable and evolutionary.
On one hand, Angular aims to provide developers with maximum stability for mission-critical applications.
As soon as more details are available, we’ll provide you with a follow-up article on how this new command can make our lives even easier.
Until then, you can use this article as a guide on how to update Angular applications to the latest version.
[I] further improved multilanguage (categories, products, products attributes, products attribute options and manufacturers).
The following fields added to the admin customer importer: disable, deleted, discount, customer id (external id for reference) Made the customer import script modular through the setting ADMIN_CUSTOMERS_I [A] admin edit order supports adding products that contains attributes [A] added several new markers that can be used for the CMS pages [B] when updating the order status the mail didnt send when having no comments [I] Pay Pal notification server impro [B] ajax page type didn't work in combination with simulate static document (fake urls).
We covered quite a lot, so let’s recap what we’ve learned.
In the first article, we learned how to: command to help update Angular applications.
On the other hand, it constantly needs to adapt and advance to support the latest changes in web technologies.
Therefore, the Angular team has decided to use a time-based release cycle with semantic versioning.