Roadmap: Next

[flovogt]

Roadmap: Next

This issue describes the currently foreseen changes for the next release of @ui5/linter. The list is not exhaustive and may change over time.

Detection improvements

• Detect usage of private/restricted UI5 APIs (CPOUI5FOUNDATION-948)
• Detect usage of experimental UI5 APIs (CPOUI5FOUNDATION-933)
• Detect mismatch of manifest.json and UI5 version (CPOUI5FOUNDATION-1108)

Autofix (JavaScript)

• Offer replacements in HTML files (CPOUI5FOUNDATION-998)
  • Rewrite bootstrap attributes (camel case -> kebap case), e.g. data-sap-ui-onInit -> data-sap-ui-on-init feat(autofix): Fix UI5 Bootstrap Parameters in HTML #779
• Migrate legacy jQuery based module definition to UI5 module definition (CPOUI5FOUNDATION-1023)
• Migrate advanced deprecated APIs (in JS and XML) (CPOUI5FOUNDATION-995)
• Offer replacements in JSON files (CPOUI5FOUNDATION-996)
  • Add missing framework libraries in manifest.json (sapui5/dependencies)
• Offer replacements in ui5 yaml files (CPOUI5FOUNDATION-997)
  • Add missing framework libraries in ui5.yaml (framework/libs)

Autofix (TypeScript)

We plan to offer the same range of autofix capabilities for TypeScript projects as for JavaScript based projects. Currently, the focus is on JavaScript projects. SAP internally this enhancement is tracked in CPOUI5FOUNDATION-1000.

Configuration

• Allow configuration of UI5 version (CPOUI5FOUNDATION-856)
  • Currently, the latest LTS version 1.136 is used
• Allow usage of OpenUI5 types (CPOUI5FOUNDATION-1093)

[pubmikeb]

In terms of roadmap discussion, it would be great to be able to audit usage of private/restricted UI5 APIs, this allows keeping the UI5 codebase in a proper way and significantly reduces risks, problems, and costs with the apps maintenance.

Regarding CPOUI5FOUNDATION-856, it allows getting rid of eslint-plugin-ui5depchk and completely switching to ui5-linter.