@sap/ux-ui5-tooling 1.6.3 → 1.6.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,10 @@
2
2
  All notable changes to this project are documented in this file.
3
3
 
4
4
  This project adheres to [Semantic Versioning](http://semver.org/) and the changelog is formatted based on [Keep a Changelog](http://keepachangelog.com/).
5
+ ## [1.6.7] - 2022-07-14
6
+ ### Changed
7
+ - The `fiori-tools-proxy` is now using the [@sap-ux/backend-proxy-middleware](https://www.npmjs.com/package/@sap-ux/backend-proxy-middleware) for proxying requests to the backend
8
+
5
9
  ## [1.6.0] - 2022-05-05
6
10
  ### Changed
7
11
  - The `fiori-tools-proxy` is now using the [@sap-ux/ui5-proxy-middleware](https://www.npmjs.com/package/@sap-ux/ui5-proxy-middleware) for proxying the UI5 sources
package/README.md CHANGED
@@ -48,7 +48,7 @@ Set this parameter to get more log information.
48
48
 
49
49
  ### [**2. Proxy**](#2-proxy)
50
50
 
51
- The proxy middleware provides you with the capabilities to connect to diffent back-end systems or to switch the SAPUI5 version of the application. The proxy is based on the [http-proxy-middleware](https://www.npmjs.com/package/http-proxy-middleware).
51
+ The proxy middleware provides you with the capabilities to connect to different back-end systems or to switch the SAPUI5 version of the application. The proxy is based on the [@sap-ux/ui5-proxy-middleware](https://www.npmjs.com/package/@sap-ux/ui5-proxy-middleware) for proxying the UI5 sources (starting with version `1.6.0`) and the [@sap-ux/backend-proxy-middleware](https://www.npmjs.com/package/@sap-ux/backend-proxy-middleware) for connecting to different back-end systems (starting with version `1.6.7`). Both `@sap-ux/ui5-proxy-middleware` and `@sap-ux/backend-proxy-middleware` are based on the [http-proxy-middleware](https://www.npmjs.com/package/http-proxy-middleware).
52
52
 
53
53
  ### Configuration Examples
54
54
 
@@ -173,7 +173,7 @@ By the default the `fiori-tools-proxy` will read the proxy configuration from th
173
173
 
174
174
  #### [UI5](#ui5)
175
175
 
176
- By using the proxy configuration one can also change the SAPUI5 version, which is used to preview the application. With the application generation also the initial ui5 configuration for the proxy is created. It looks e.g. like this.
176
+ By using the proxy configuration one can also change the SAPUI5 version, which is used to preview the application. By using the `version` parameter one can change the SAPUI5 version as follows:
177
177
 
178
178
  ```
179
179
  - name: fiori-tools-proxy
@@ -187,7 +187,7 @@ By using the proxy configuration one can also change the SAPUI5 version, which i
187
187
  version: 1.78.0
188
188
  ```
189
189
 
190
- By using the `version` parameter one can choose the SAPUI5 version which will used when `npx fiori run` is executed.
190
+ Starting with `ux-ui5-tooling` version `1.4.7`, if the `version` property is not set in the `ui5.yaml`, then the `minUI5Version` from `manifest.json` will be used for the application preview. If the `version` property is set, but it is empty, then the `latest` SAPUI5 version from https://ui5.sap.com will be used for the application preview. For any other case the value of the `version` property will be used for the application preview.
191
191
 
192
192
  **Note:** all UI5 requests are routed through the proxy. Sometimes this can cause performance issues. If you don't want route the UI5 requests through the proxy, then you can set parameter `directLoad: true`. This will inject the UI5 url in the HTML file of the application and thus the UI5 libs will be loaded directly.
193
193