The decision everything else follows from: one ABAP class per app, no generated artifacts, no tables that describe a screen.
| {k} | {a} |
|---|
| abap2UI5 | A tool that stores apps as configuration | |
|---|---|---|
| {k} | {a} | {b} |
So abap2UI5 needs no rule of its own. Every rule that already applies to ABAP — naming conventions, code review, ATC, the four-eyes principle on transports — applies to an app without any change. A system closed for repository changes is closed for abap2UI5 apps.
@@ -343,7 +361,7 @@ const doors = [→ Who Uses abap2UI5? and References have the full lists - both are open for your own row.
+→ Running abap2UI5, or written about it? Add your row, or write to contact@abap2UI5.org.