Continuing the development and support for Angular 1, we are announcing the following huge release, 1.6.0, which has been in development since May 2016.

In this release, we have included various helpful features that ought to enhance the developer experience and we have taken care of the security of Angular 1 considerably further. We have additionally evacuated a bunch of expostulated features that make the code base less demanding to maintain and in numerous cases enhances performance.

New Features:

Here are the most huge new features accessible in 1.6.0.

Inheriting ngModelOptions:

When defining model options using the ngModelOptions directive, you would now be able to inherit options from precursor ngModelOptions directives. This implies developers can bring together basic model options instead of repeating themselves over their whole HTML.

Alignment with jQuery 3:

JQuery 3 was released in 2016 and contains a few changes that left our own jqLite usage out of synchronizing. In this release, we have changed jqLite so it coordinates the conduct of jQuery 3.

Controller binding pre-task:

We no longer pre-allocate bindings onto instances of directive controllers previously calling their constructors. This conduct was not in keeping with how JavaScript protest instantiation functions and furthermore kept developers from using local JavaScript classes where accessible.

Presently all directive controllers should utilize $onInit to initialize their state, where the bindings are ensured to be prepared. This is additionally nearer to the semantic of Angular 2 segments.

Better support for range inputs:

In Angular 1.5.x (from 1.5.10 and later) you have to manually opt-in to this support since the conduct of local range inputs required a change to how ngModel has taken care of updates to the value:

Angular 1.6 presently completely supports as a matter of course without having to opt-in.

It requires the model to be an number and it will set the model to a number.

It just supports setting minimum and most extreme values through the min/max attributes.

It pursues the program conduct of never allowing an invalid value: when the program changes over an invalid value to a valid value, the model is set to this new valid value.

Security Improvements:

There have been various submits that have enhanced or illuminated the security of Angular 1 applications. Here is a portion of the features.

Mozilla Addons:

Because of some strengthening work we have done to make it harder to autobootstrap Angular in program augmentations, all versions of Angular from 1.5.9/1.6.0 onwards are currently whitelisted as sheltered to use in Mozilla Addons.

Expression sandbox evacuation:

In this version of Angular, we have evacuated the Angular expression sandbox include. A few developers were incorrectly using this in an endeavor to forestall XSS assaults to their formats. To clarify this ought not to be depended upon along these lines we have settled on the choice to evacuate it totally.


JSONP is currently anchored by the $sce benefit, similarly that other noteworthy assets are in Angular 1. JSONP URLs should now be white listed or unequivocally trusted before Angular will enable a demand to the endpoint. Further, the syntax for JSONP URLs is presently more secure, by disallowing the JSON_CALLBACK from the URL format and requiring that the callback is given by means of the jsonpCallbackParam config param for solicitations.

Different Changes:

There are more than 70 noteworthy submit somewhere in the range of 1.5 and 1.6. You can find a nitty-gritty rundown of the considerable number of changes, including bug fixes and performance improvements in our Next Article.

Migrating from 1.5 to 1.6:

While there are various breaking changes somewhere in the range of 1.5 and 1.6, numerous just influence extremely uncommon corner cases. There are a couple of noteworthy changes that you ought to know about and we have a far-reaching migration manual for the guarantee that your migration goes easily.

Past Version Support:

We trust that Angular 1.6 is presently the best Angular 1 version out there and that you should refresh your applications to utilize it.

They continue to support Angular 1.2 with security patches as it is the last version of Angular to support Internet Traveler 8 and starting now and into the foreseeable future Angular 1.5 will get genuine bug fixes and security patches.

Angular 1.6 will get normal non-breaking change releases throughout the following a half year, and we will go for the release of Angular 1.7 containing any important breaking changes by Summer 2017.

Author's Bio: 

Infocampus is the Best Angularjs Training Institute in Bangalore with Real-Time Training and Live Projects. Infocampus provides 100% Placement Assistance.

For Demo call: 08884166608 / 09740557058