Angular 5.0 new ship arrives.

Angular 5.0 new ship arrives.

Google now released new Angular 5.0 version as pentagonal-donut. A new cookie is ready now we have to taste it. The Angular 5.0.0 upgrade itself centers on making the framework faster, smaller, and easier to use. Angular now requires TypeScript 2.4.x.

How’s a new taste of Angular 5?

What are the new features angular 5 is come up with?

  1. Build Optimiser
  2. Angular Universal State Transfer API and DOM Support
  3. Compiler Improvements
  4. Improved Decorator Support
  5. Internationalised Number, Date, and Currency Pipes. a document comparing the pipe behavior between v4 and v5.
  6. Replace the ReflectiveInjector with StaticInjector.
  7. Zone speed improvements
  8. exportAs to exporting a directive with multiple names.
  9. HttpClient.
  10. CLI v1.5.
  11. Angular Forms adds updateOn Blur / Submit.
  12. Support for RxJS 5.5 and later version
  13. New Router Lifecycle Events.

How to use Angular5.0 or How to update it to the latest version.

Google had designed update guide use this. With the help of this link you can update version from angular 2.0 up to angular 5.0.

Update guide from 4.0 to 5.0

Angular Update Guide — 4.0 -> 5.0 for Basic Apps

Before updating

Rename your template tags to ng-template

Replace downgradeComponent, downgradeInjectable, UpgradeComponent, and UpgradeModule imported from @angular/upgrade. Instead use the new versions in @angular/upgrade/static.

During the update

If you rely on the date, currency, decimal, or percent pipes, in 5 you will see minor changes to the format. For applications using locales other than en-us, you will need to import it and optionally locale_extended_frfrom and registerLocaleData(local).

Update all of your dependencies to the latest Angular and the right version of TypeScript. If you are using Linux/Mac, you can use:

npm install @angular/{animations,common,compiler,compiler-cli,core,forms,http,platform-browser,platform-browser-dynamic,platform-server,router}@'^5.0.0' [email protected] [email protected]'^5.5.2'

npm install [email protected] --save-exact

After the update

Switch from HttpModule and the Http service to HttpClientModule and the HttpClient service. HttpClient simplifies the default ergonomics (You don’t need to map to json anymore) and now supports typed return values and interceptors. Read more on

For more details explore more on below link

If you enjoyed this article, please don’t forget to Clap.

For more stories.

Lets connect on Stackoverflow , LinkedIn , Facebook& Twitter.

Git workflow.

Git workflow.

Git is a version control system for tracking changes in computer files and coordinating work on those files among multiple people. Git is a SCM (source code management) in software development.

Git was created by Linus Torvalds in 2005 for development of the Linux kernel, with other kernel developers contributing to its initial development.[12] Its current maintainer since 2005 is Junio Hamano.

Three main workflows of git

When we are using git there are three main workflows that can be adopted.

  1. Centralized workflow
  2. Feature Branch Workflow
  3. Gitflow workflow

1.Centralized workflow:-

The most popular workflow among developers and the entry stage of every project.

The idea is quite simple. There is only one central master repository. Each developer clones the repository works locally on the code makes a commit with changes, and push it to the central master repository for other developers to pull and use in their work.

2. Feature Branch workflow:-

In feature branch workflow user create feature wise branch. This useful when you want to do some experiment. After complete development of that code user can then merge the code to the final branch. Branches are independent “tracks” of developing a project. For each new feature, a new branch should be created, where the new feature is developed and tested. Once the feature is completed and ready to live, the branch can be merged into the master branch.

3. Gitflow workflow:-

In this type, a user takes advantage of git branching. This is somehow similar to a feature branch workflow but there are some differences. In this type, a user creates the branch based on the software development lifecycle. Like separate branches for features once all the features are ready then merge those feature branch inside the development branch once everything is verified and tested then merge that branch to release branch or some SIT branch. Or we can create them based on the product version as well.

The above is a simple example. This, not a mandatory to workflow as it is.

You can customize the workflow based on project requirement, team size and team expertise using the git and teams fine grain structure. For my personal project, I use a centralized workflow. For large enterprise project and in CI and CD implementation scenario people prefer the git-flow workflow.

So which approach do you choose? and Why? Let me know in comments.

For more stories.

Lets connect on Stackoverflow , LinkedIn , Facebook& Twitter.