Skip to content

Commit db51dc4

Browse files
authored
update
1 parent f75a0c6 commit db51dc4

File tree

2 files changed

+6
-51
lines changed

2 files changed

+6
-51
lines changed

docs/advanced/tools/abapgit.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
# abapGit
22

3-
This project uses [**abapGit**](https://github.com/abapGit/abapGit) to distribute its code and manage version control efficiently.
3+
This project uses [abapGit](https://github.com/abapGit/abapGit) to distribute its code and manage version control efficiently.
44

55
#### git Client
66
All projects artefacts are developend on an ABAP System and stored via abapGit in a GitHub repository. This makes hte project easy to install on any system for customers. Updates are always distributed at sofort and can be pulled by every csutomer.
77

88
#### Contribution
99

10-
Contributions can be easily made via **Pull Requests** on GitHub. Simply create a new **Pull Request** and update your code using **abapGit**.
10+
Contributions can be easily made via Pull Requests on GitHub. Simply create a new Pull Request and update your code using abapGit.
1111

12-
#### abap2UI5 Apps as abapGit Artefacts
13-
In addition to the **abap2UI5** project, all developed **abap2UI5** apps are also stored as **abapGit** objects. This allows you to manage them in any Git repository. As a result, **abap2UI5** apps do not require manual deployment like traditional **UI5** apps. You can install multiple **abap2UI5** apps with a single **abapGit** pull. This also works seamlessly in **ABAP Cloud** contexts, reducing deployment effort and keeping everything centralized in the backend.
12+
#### Apps as abapGit Artefacts
13+
In addition to the abap2UI5 project, all developed abap2UI5 apps are also stored as abapGit objects. This allows you to manage them in any Git repository. As a result, abap2UI5 apps do not require manual deployment like mormal UI5 apps. You can install multiple abap2UI5 apps with a single abapGit pull. This also works seamlessly in ABAP Cloud contexts, reducing deployment effort and keeping everything centralized in the backend.

docs/advanced/tools/open_abap.md

+2-47
Original file line numberDiff line numberDiff line change
@@ -1,51 +1,6 @@
11
---
22
outline: [2, 4]
33
---
4-
# Setup
4+
# open-abap
55

6-
<i class="fa-brands fa-github"></i> [Repository](https://github.com/abap2UI5/setup)
7-
8-
abap2UI5 can be used with open-abap, providing the ability to run unit tests in GitHub Actions, perform frontend testing, and execute samples directly in your browser—without needing a backend.
9-
10-
<img width="800" alt="image" src="https://github.com/user-attachments/assets/4306fc51-a926-44e3-9572-e4f3fe0eb419">
11-
12-
### Functionality
13-
* Downporting with [abaplint](https://abaplint.org/)
14-
* Transpiling to JS with [abaplint/transpiler](https://github.com/abaplint/transpiler)
15-
* Running on Node.js with [open-abap](https://github.com/open-abap/express-icf-shim)
16-
* Service exposing via [express-icf-shim](https://github.com/open-abap/express-icf-shim)
17-
* Browser Tests with [Playwright](https://playwright.dev/)
18-
* Webpacking, Unit Testing...
19-
20-
Pull the repository and try out:
21-
22-
### Downport & Transpile
23-
```
24-
npm run init
25-
npm run build
26-
```
27-
### Run Unit Tests
28-
```
29-
npm run unit
30-
```
31-
### Run Webservice
32-
```
33-
npm run express
34-
```
35-
### Run Playwright Tests
36-
```
37-
npm run init_play
38-
npx playwright install --with-deps && npm i
39-
npx playwright test
40-
```
41-
42-
### Webpack Build Strategy
43-
44-
1. Clone repositories into /src/
45-
2. Downport /src/ into /downport/
46-
3. Transpile with express-icf-shim into /output/
47-
4. Webpack backend + frontend + database into folder build
48-
49-
```
50-
npm run webpack:build
51-
```
6+
abap2UI5 uses [open-abap](https://github.com/open-abap) to run unit tests, perform frontend testing, and run samples directly in your browser—without needing a backend.

0 commit comments

Comments
 (0)