You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on SAP/openui5@c782ce9 , I encountered the following issue with the ui5-migration tooling:
When the source of a module contains a global reference to the export of the same module, then the 'migrate' command adds a dependency to self and tries to use the resulting import whenever the export value is references. This happens in nearly each library.js module, but also in a few others.
While working on SAP/openui5@c782ce9 , I encountered the following issue with the ui5-migration tooling:
When the source of a module contains a global reference to the export of the same module, then the 'migrate' command adds a dependency to self and tries to use the resulting import whenever the export value is references. This happens in nearly each library.js module, but also in a few others.
Before
After (please also note that the 'library dependency' comments are also misplaced)
To reproduce, you can execute the following commands
The text was updated successfully, but these errors were encountered: