Skip to main content

New features, performance improvements, and bug fixes In Angular 5.

Angular 5 is going to be a much better Angular. The Angular version 5 will be fully released in September/October 2017.

Angular 5 contains a bunch of new features, performance improvements, and a lot of bug fixes.

  • Make AOT the default
  • Watch mode
  • Type checking in templates
  • More flexible metadata
  • Remove *.ngfactory.ts files
  • Better error messages
  • Smooth upgrades
  • Tree-Shakeable components
  • Hybrid Upgrade Application

Angular 5 - Performance Improvements

  • Use of addEventListener for the faster rendering and it is the core functionality.
  • Update to new version of build-optimizer.
  • Added some Improvements on the abstract class methods and interfaces
  • Remove decorator DSL which depends on Reflect for Improve the Performance of Apps and This is the core functionality.
  • Added an option to remove blank text nodes from compiled templates
  •  Switch Angular to use Static-Injector instead of Reflective-Injector.
  • Improve the applications testing.
  • Improve the performance of hybrid applications
  • Improvements on Lazy loading for Angular

Some improvements on HttpClient – This is used for applications to communicate with backend services over the HTTP protocol!

  • Improvement on Type-checking the response
  • Improvement on Reading the full response
  • Improvement on Error handling and fetching error details
  • Improvement on Intercepting all requests or responses
  • Improvement on Logging
  • Improvement on Caching
  • Improvement on XSRF Protection

Angular 5 - Added Features

  • Added Representation of Placeholders to xliff and xmb in the compiler
  • Added an Options Arg to Abstract Controls in the forms controls
  • Added add default updateOn values for groups and arrays to form controls
  • Added updateOn blur option to form controls
  •  Added updateOn submit option to form controls
  • Added an Events Tracking Activation of Individual Routes
  • Added NgTemplateOutlet API as stable in the common controls
  • Create StaticInjector which does not depend on Reflect polyfill
  • Added [@.disabled] attribute to disable animation children in the animations


Angular 5 - Router Life Cycle Events

Added new router lifecycle events for Guards and Resolvers

  • GuardsCheckStart,
  • GuardsCheckEnd,
  • ResolveStart and
  • ResolveEnd

Angular 5 - Bug Fixes

  • Fixed compilation error by using the correct type for providers
  • Skip PWA test when redeploying non-public commit
  • Don't strip CSS source maps. This is the compiler related fix
  • Remove tsickle (language-service) dependency
  • Support persisting dynamic styles within animation states
  • Ignore @import in multi-line css
  • Fix platform-browser-dynamic
  • Forbid destroyed views to be inserted or moved in VC
  • Support persisting dynamic styles within animation states


Labels:
Location: Chicago, IL, USA

Comments

Post a Comment

Popular posts from this blog

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests: Write tests for all public methods Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early. public class Calculator { public int Add(int a, int b) { return a + b; } } [TestClass] public class CalculatorTests { [TestMethod] public void Add_ShouldReturnCorrectSum() { // Arrange Calculator calculator = new Calculator(); int a = 1; int b = 2; // Act int result = calculator.Add(a, b); // Assert Assert.AreEqual(3, result); } } Test boundary conditions  Make sure to test boundary conditions, such a...
Post a Comment
Read more

What to choose between .NET Core and .NET?

 .NET Framework is a better choice if you: you don't have enough time time to learn new technology. Need a stable environment to work in. Have nearer release schedules. you are already working on an existing app and extending its functionality. If already have an existing team with .NET expertise and building production-ready software. Do not want to deal with continuous upgrades and changes. Building Windows client applications using Windows Forms or WPF .NET Core is a better choice if you: IF you wanted to deploy your app on Windows, Linux, and Mac operating systems. Are not afraid of learning new things. Are not afraid of breaking and fixing things since .NET Core is not fully matured yet. When you are learning .NET. work on open source.
Post a Comment
Read more