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
Is your feature request related to a problem? Please describe.
Data source URI in manifest.json should not start with a slash in order to UI5 application work properly in a FLP.
Describe the solution you'd like
It would be nice to have a builder task or setting that checks manifest.json and strips off leading slash from a data source URI during a building of an application to ensure that URI is correct automatically.
Describe alternatives you've considered
There is a such feature in @sap/grunt-sapui5-bestpractice-build module that is not supported any more and should be replaced with @ui5/builder.
It would be great to have this feature directly in ui5-tooling. At the moment the Fiori Application Generator uses a custom task using "webide-extension-task-updateManifestJson" to update the manifest.json when deploying to Cloud Foundry.
As far as I remember, SAP Build Work Zone, standard edition a.k.a "Central Launchpad on CF" does not support absolute URLs at all. So the url should be relative in the source manifest.json.
I wonder why you not adjust the source manifest.json to make it relative right from the beginning?
Is your feature request related to a problem? Please describe.
Data source URI in manifest.json should not start with a slash in order to UI5 application work properly in a FLP.
Describe the solution you'd like
It would be nice to have a builder task or setting that checks manifest.json and strips off leading slash from a data source URI during a building of an application to ensure that URI is correct automatically.
Describe alternatives you've considered
There is a such feature in @sap/grunt-sapui5-bestpractice-build module that is not supported any more and should be replaced with @ui5/builder.
Additional context
Example of a data source section of manifest.json
The text was updated successfully, but these errors were encountered: