Sharing Top Content from the Angular-sphere.

An Upgrade Path to Angular at Thomson Reuters – Angular Blog

An Upgrade Path to Angular at Thomson Reuters

  • Teams need to understand the implications of each approach so that they can choose the best option for their product.ng-rosettaTo help teams understand these patterns, we built a series of reference projects known as series was published internally as a living example of Angular migration patterns and is regularly updated…
  • Lastly Fruit20 shows a full Angular rewrite of the project.Here is a breakdown of each project, it’s target pattern, and the various tools and patterns used.Project Name: Fruit1XAngular Pattern – AngularJS ControllerAs PatternNotable Tools Patterns – Grunt, TypeScript1 w/Typings, TSLint, ui-grid, ui-router, bootstrap, ui-bootstrap.
  • 3rd party dependencies delivered via npm.Project Name: Fruit20–15Angular Pattern – Angular/AngularJS Hybrid Patter (ngUpgrade + AngularJS Component Pattern App hosted inside an Angular app)Notable Tools Patterns – Fruit15 Patterns plus ng-upgrade.
  • Still other patterns simply needed to be experimented with and massaged to unlock.Open sourcing ng-rosettaAs a means to give back to the open source community, and in hopes of providing reference material to the next round of developers that need to explore these scenarios, I’ve published the entire ng-rosetta series…
  • One example of these shared tools is an AngularJS Seed Project that demonstrates recommended patterns such as the AngularJS Component pattern, the use of hierarchical routes via ui-router and patterns for front-end tests builds.

Stephen Fluin: This is a guest post from David Owen, who is a leader of front-end strategy at Thomson Reuters In the Tax & Accounting division of Thomson Reuters, we build software products for…

An Upgrade Path to Angular at Thomson ReutersStephen Fluin: This is a guest post from David Owen, who is a leader of front-end strategy at Thomson ReutersIn the Tax Accounting division of Thomson Reuters, we build software products for corporations, governments, accounting firms, financial institutions and more. We have a significant investment in AngularJS and Angular, and believe that migrating to the latest version is key to delivering the next generation of these products.Upgrading to AngularWhen looking at options for upgrading our existing projects to Angular, equal measure is given to both the Hybrid pattern (via ngUpgrade) and a phased approach to a full rewrite. Teams need to understand the implications of each approach so that they can choose the best option for their product.ng-rosettaTo help teams understand these patterns, we built a series of reference projects known as series was published internally as a living example of Angular migration patterns and is regularly updated as new versions and patterns evolve. The series is regularly presented and referenced during upgrade strategy discussions and has been included in training material available to our Front-end Framework Community.Projects Contained in ng-rosettaTo summarize, we have a starting project (Fruit1X, for Angular 1.x), that uses older patterns (ControllerAs, Grunt, etc). The rest of the sample projects demonstrate how that application looks after conversion to the target pattern. Fruit15 (for Angular 1.5) shows the Fruit app converted to the AngularJS Component Pattern and implements newer tooling (Webpack, and npm delivery). Fruit20–15 (for Angular/AngularJS 1.5) shows the Hybrid…

An Upgrade Path to Angular at Thomson Reuters – Angular Blog

Comments are closed, but trackbacks and pingbacks are open.