Migration Tooling
for UI5 Evolution
Tobias Sorn, SAP
June 28, 2019

Motivation

The one constant in software development:

Change

Change in UI5 (Evolution)

  • Use AMD
  • Perform async calls
  • Remove global variables (e.g. Decoupling of jQuery)
  • Use native browser functionality if possible
  • Split modules into smaller chunks

Change in app coding

  1. Read documentation and blog posts
  2. Identify places in your code
  3. Modify your code
  4. Hope

Manual Effort

UI5 Migration

  • Analyze Codebase
  • Migrate Codebase

@ui5/migration

How to use

Use UI5 Migration in your apps with 3 simple steps:
  1. npm install @ui5/migration -g
  2. ui5-migration migrate .
  3. Verify replacements
  4. ???
  5. Profit

Demo time

Noteworthy

  • Manual verification is recommended but not mandatory
  • Code might be re-formatted
  • Factory API changes are not yet to covered, e.g. sap.ui.component vs. Component.create()

Useful links

UI5 Migration @ui5/migration
Feedback / Issues Issues
Documentation SDK Documentation
UI5ers Buzz UI5ers Buzz Blog

Q & A

WebIDE integration? Would be awesome but nothing planned yet
Mandatory for all SAP apps? In my opinion recommended, but not mandatory
If not migrated does code break with new version? UI5 stays backward compatible and code migration is not required for version upgrades (but recommended)
Thank you.
Contact information:

Tobias Sorn
Senior Developer
tobias.sorn@sap.com