@sap-ux/fiori-mcp-server 1.4.1 → 1.5.1
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/README.md +17 -7
- package/dist/data/embeddings/metadata.json +1 -1
- package/dist/data/embeddings/records.jsonl +751 -751
- package/dist/index.js +646 -626
- package/package.json +7 -8
package/README.md
CHANGED
|
@@ -170,22 +170,32 @@ Note: the results are based on the most recent indexed version of UI5 documentat
|
|
|
170
170
|
#### `list_fiori_apps`
|
|
171
171
|
Scans a specified directory to find existing SAP Fiori applications that can be modified.
|
|
172
172
|
|
|
173
|
-
#### `
|
|
174
|
-
|
|
173
|
+
#### `list_sap_systems`
|
|
174
|
+
Lists all SAP systems stored in the user's environment (e.g. SAP Fiori tools system store). Use this when the user references a SAP system by name before calling `download_odata_service_metadata` or generating a Fiori application.
|
|
175
175
|
|
|
176
|
-
|
|
176
|
+
#### `download_odata_service_metadata`
|
|
177
|
+
Downloads the EDMX metadata of a specific OData service from a SAP system and saves it as `metadata.xml`. Use this before calling `generate_fiori_app_odata` when the user provides a SAP system reference or service URL.
|
|
178
|
+
|
|
179
|
+
#### `generate_fiori_app_odata`
|
|
180
|
+
Generates a new SAP Fiori UI application for OData (non-CAP) projects, for example [ABAP RESTful Application Programming Model](https://pages.community.sap.com/topics/abap/rap)-based OData services.
|
|
181
|
+
|
|
182
|
+
#### `generate_fiori_app_cap`
|
|
183
|
+
Generates a new SAP Fiori UI application within an existing [SAP Cloud Application Programming Model (CAP)](https://cap.cloud.sap/) project.
|
|
184
|
+
|
|
185
|
+
#### `list_functionality` (Step 1 of 3)
|
|
186
|
+
Gets the list of supported **modification** functionalities for an existing SAP Fiori application. Requires a valid absolute path to the application.
|
|
187
|
+
|
|
188
|
+
The supported modifications are:
|
|
177
189
|
|
|
178
|
-
- Generating an SAP Fiori elements app within an [SAP Cloud Application Programming Model (CAP)](https://cap.cloud.sap/) project
|
|
179
|
-
- Generating an SAP Fiori elements app for an existing OData service, for example, an [ABAP RESTful Application Programming Model](https://pages.community.sap.com/topics/abap/rap)-based OData service
|
|
180
190
|
- Adding and deleting pages from an app
|
|
181
191
|
- Adding and modifying controller extensions
|
|
182
192
|
- Modifying `manifest.json` properties depending on the app, for example, adding a layout based on the flexibility of the programming model or enabling initial load
|
|
183
193
|
|
|
184
194
|
#### `get_functionality_details` (Step 2 of 3)
|
|
185
|
-
Gets the required parameters and detailed information for a specific functionality to
|
|
195
|
+
Gets the required parameters and detailed information for a specific functionality to modify an existing SAP Fiori application.
|
|
186
196
|
|
|
187
197
|
#### `execute_functionality` (Step 3 of 3)
|
|
188
|
-
Executes a specific functionality to
|
|
198
|
+
Executes a specific functionality to modify an existing SAP Fiori application with provided parameters.
|
|
189
199
|
|
|
190
200
|
## [Logging](#logging)
|
|
191
201
|
|