Forcefully add some classes (like sap/ui/core/ComponentSupport) to a self-contained build

[kristian]

Expected Behavior

Only the sap-ui-custom.js boostrap JavaScript should be loaded when a self-contained build is chosen. The boostrap should contain all classes needed to run the application.

Current Behavior

Some files are anyways loaded seperately, such as the sap/ui/core/ComponentSupport in case the data-sap-ui-oninit boostrap option is chosen to load a component.

Steps to reproduce the issue

1. Change the index.html file of the samle application to load the ComponentContainer via the data-sap-ui-oninit="module:sap/ui/core/ComponentSupport" method
2. Build & serve the sample app self-contained

Context

• OS/Platform: Windows
• Node.js Version: 10.11.0
• npm Version: 6.4.1
• Browser (if relevant): Chrome Dev.
• Other information: Tested on 1.59.0

Affected components

• [x] ui5-builder
• [ ] ui5-server
• [ ] ui5-cli
• [ ] ui5-fs
• [ ] ui5-project
• [ ] ui5-logger

[matz3]

Until we have worked out a solution, a workaround would be to manually add the dependency e.g. the Component.js module:

sap.ui.define([
  "sap/ui/core/UIComponent",
  "sap/ui/core/ComponentSupport"
], function(UIComponent) {
  "use strict";
  return UIComponent.extend("sap.ui.demo.todo.Component", {
    metadata: {
      manifest: "json"
    }
  });
});

[pubmikeb]

@matz3 , are there any news on the subject?

[matz3]

@pubmikeb No, unfortunately not.