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
Copy file name to clipboardExpand all lines: step-by-step.md
+15-6Lines changed: 15 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This guide explains step-by-step and command-by-command how you get to a complet
4
4
5
5
While you can get started faster by just copying and modifying the entire *Hello World* app, this step-by-step guide will help you understand every bit and piece of the setup and how the pieces fit together.
6
6
7
-
It consists of ten steps, but in fact only the first half is really related to TypeScript. The remaining five steps are about adding the UI5 tools to the project and wrapping everything up nicely, so these steps apply more or less to any UI5 application project.
7
+
It consists of ten steps, but in fact only the first four steps and step six are really related to TypeScript. The other steps are about adding the UI5 tools to the project and wrapping everything up nicely, so these steps apply more or less to any UI5 application project.
8
8
9
9
## Table of Contents
10
10
@@ -238,7 +238,7 @@ metadata:
238
238
type: application
239
239
```
240
240
241
-
For running UI5 applications with the UI5 Tooling we also need some additional `framework` information like framework `name` and `version`) and the required libraries and theme libraries. Now put the following content in your `ui5.yaml` (please adopt the `metadata>name` to `ui5.typescript.helloworld`):
241
+
For running UI5 applications with the UI5 Tooling we also need some additional `framework` information (like framework `name` and `version`) and the required libraries and theme libraries. Now put the following content in your `ui5.yaml` (please adopt the `metadata>name` to `ui5.typescript.helloworld`):
242
242
243
243
```yaml
244
244
specVersion: "3.0"
@@ -284,8 +284,8 @@ What you can do now: create a simple `test.html` file in the `webapp` folder and
284
284
src="resources/sap-ui-core.js"
285
285
data-sap-ui-libs="sap.m"
286
286
data-sap-ui-theme="sap_horizon"
287
-
data-sap-ui-compatVersion="edge"
288
-
data-sap-ui-oninit="onInit"
287
+
data-sap-ui-compat-version="edge"
288
+
data-sap-ui-on-init="onInit"
289
289
data-sap-ui-async="true"
290
290
></script>
291
291
<script>
@@ -307,7 +307,7 @@ What you can do now: create a simple `test.html` file in the `webapp` folder and
307
307
</html>
308
308
```
309
309
310
-
After you can start the `test.html` running inside the development server of the UI5 CLI Tooling:
310
+
After that, you can start the `test.html` running inside the development server of the UI5 CLI Tooling:
Now it's time to write down the various commands used so far as scripts in `package.json`, so you don't need to type them every time they are used.
475
475
476
+
While we are at it, we can add one more command: the `ui5-linter`, which complements eslint with code checks that make sure the code adheres to the best practices and is ready for UI5 2.0:
477
+
478
+
```sh
479
+
npminstall--save-dev @ui5/linter
480
+
```
481
+
482
+
It can be invoked using `npxui5lint`.
483
+
476
484
Change the `"scripts"` section in the `package.json` file to have the following content. All scripts have already been used and explained earlier, so there is nothing new here, it's just for convenience.
477
485
478
486
```json
@@ -482,7 +490,8 @@ Change the `"scripts"` section in the `package.json` file to have the following
0 commit comments