The minor release of Angular version 2.1.0 –incremental –metamorphosis is finally out. In this release, they have come up with an adoption of Semantic Versioning, which means there are not many changes added in this release so that they can replace it with 2.0.x.
New features of Angular 2.1.0
- The capabilities of Angular connect : With the previous version, users were able to access lazy loaded content only after round trip to the server. In this version, routers have great support for preloading of the lazy loaded modules where users can experience the best parts of both the worlds.
- Animation in Angular have received some improvements by adding :enter and :leave Aliases for common void => * and* => void state changes.
Also Read : Google releases Angular version 2.0.0
In the previous version 2.0.0 Angular release, they have set some standards for the development processes:
- They have come up with the semantic versioning: Which means the version updations are relevant to the numbers. These releases do not affect the functionality, only minor changes will be added. Usually breaking changes will be announced in the major releases.
- For future planning purpose they have come up with time-based cycles: The cycles have been planned as per the below schedule so that developers can easily adapt to the changes.
They have come with Deprecation policy so that developers will be informed in prior about the API changes: Breaking changes are troublesome, but these changes are required as part of innovation. Dependencies or transitions are done in the platform itself. To get easily adapted to the changes, they are implementing deprecation policy and trying to minimize the number of breaking changes in Angular.
They have given the proper differentiation between the stable and experimental APIs: If you have gone through the Angular API docs, you have might have noticed some marked APIs as experimental. Experimental APIs are good enough to be in production, only field testing is required to validate and work well for different use cases. Semantic versioning is followed by experimental APIs but they don't follow deprecation policy. When you start working with Experimental APIs changes are expected but they do not have deprecation path.
The Scope of their Public API surface is well defined: Angular is a group of packages, tools, and sub-projects. To avoid the usage of private APIs unexpectedly, terms and conditions are documented in public API surface.