@open-rap/compiler 0.1.0 → 0.1.2

package/README.md

@@ -1,6 +1,6 @@
 # @open-rap/compiler
 
-The compiler of [Open RAP Runtime](https://clementringot.github.io/RAP-Transpiler/): CDS, BDEF,
+The compiler of [Open RAP Runtime](https://clementringot.github.io/Open-Rap-Runtime/): CDS, BDEF,
 SRVD and DCL parsers, intermediate representation, generators (SQL, OData V4 `$metadata`,
 transpiled ABAP, OpenUI5 UI) and the command line.
 

package/dist/authoring/new.js

@@ -323,7 +323,7 @@ finds the MCP server of rapt (tools \`rapt_check\`, \`rapt_generate\`, \`rapt_do
 - Write ABAP Cloud and CDS as in the ABAP Development Tools; RAP managed, with or without draft.
 - Run \`rapt check .\` after every change until there is no error; the codes are explained in
   the documentation (tile *Documentation* of \`rapt dev\`, the tool \`rapt_docs_read\` of
-  \`rapt agent\`, or https://clementringot.github.io/RAP-Transpiler/docs/diagnostics.html).
+  \`rapt agent\`, or https://clementringot.github.io/Open-Rap-Runtime/docs/diagnostics.html).
 - Keep \`rapt/config.json\` in mode \`standard\` when the BO must activate on SAP; \`enhanced\`
   allows Open RAP Runtime extensions (mandatory fields checked automatically, managed BO on a
   custom entity).

package/dist/cli.js

@@ -71,8 +71,8 @@ Options:
   --warnings-as-errors
   -h, --help
 
-Documentation: https://clementringot.github.io/RAP-Transpiler/docs/
-Report a bug or request a feature: https://clementringot.github.io/RAP-Transpiler/feedback.html
+Documentation: https://clementringot.github.io/Open-Rap-Runtime/docs/
+Report a bug or request a feature: https://clementringot.github.io/Open-Rap-Runtime/feedback.html
 `;
 function report(diagnostics) {
     for (const d of diagnostics.sorted()) {

package/dist/gen/app/index.js

@@ -228,7 +228,7 @@ ${rows.join("\n")}
 function readme(model, name, destinations = []) {
     return `# ${name}
 
-Application generated by [Open RAP Runtime](https://clementringot.github.io/RAP-Transpiler) from the
+Application generated by [Open RAP Runtime](https://clementringot.github.io/Open-Rap-Runtime) from the
 RAP service definition \`${model.service.name}\`: an OData V4 service (\`${model.service.path}\`), the
 managed RAP runtime with the transpiled behavior pool, and an OpenUI5 UI (List Report / Object
 Page) at \`/ui/\`.

package/dist/gen/launchpad/index.js

@@ -115,7 +115,7 @@ function readme(name, model) {
     const tiles = model.groups.flatMap((g) => g.tiles.map((t) => ({ group: g.title, tile: t })));
     return `# ${name}
 
-Launchpad generated by [Open RAP Runtime](https://clementringot.github.io/RAP-Transpiler): the entry
+Launchpad generated by [Open RAP Runtime](https://clementringot.github.io/Open-Rap-Runtime): the entry
 point of the applications, as the SAP Fiori launchpad, built with OpenUI5. It shows the tiles
 assigned to the roles of the user, opens the applications at \`/apps/<id>/\` and forwards the
 requests of their UIs to their services: the browser sees a single origin and logs in once.

package/docs/DECISIONS.md

@@ -1496,8 +1496,8 @@ correspond to points 1 to 13 of §11 of PLAN.md. The milestones M1 to M6 are tho
   (npm organization `open-rap`), the VS Code extension `open-rap-runtime-vscode` ("Open RAP
   Runtime"). Unchanged, so that existing projects keep working: the `rapt` command, the `rapt/`
   folder of the projects, the `.rapt/` build folder, the `rapt_*` tables, the `ZRAP_*` ABAP
-  objects. The URL of the website follows the name of the GitHub repository
-  (`RAP-Transpiler`) until it is renamed.
+  objects. The URL of the website follows the name of the GitHub repository, renamed
+  `Open-Rap-Runtime` (https://clementringot.github.io/Open-Rap-Runtime/).
 - **Why**: "Open" says open source and without proprietary SAP libraries; "RAP Runtime" says
   what the application runs. The website states that the project is not affiliated with SAP SE.
 - **Tests**: the whole suite (package names, generated applications with `vendor/open-rap-*`,
@@ -1505,6 +1505,8 @@ correspond to points 1 to 13 of §11 of PLAN.md. The milestones M1 to M6 are tho
 
 ## D71 — Feedback: a public feedback repository and a form on the website
 
+_The issues moved to the repository itself once public: see D74._
+
 - **Context**: the repository is private, so its issues are not open to the users; bug reports
   and feature requests had no place.
 - **Decision**: a public repository, `ClementRingot/open-rap-runtime-feedback`, holds the issues,
@@ -1524,3 +1526,59 @@ correspond to points 1 to 13 of §11 of PLAN.md. The milestones M1 to M6 are tho
   fields, prefill from the query string, URL of the issue with the fields of the bug form,
   fields of the feature form, mobile without horizontal scrolling).
 
+
+## D72 — Extension builds: progress, floorplan prompts; the website serves the released .vsix
+
+- **Context**: in VS Code, *Build the application* kept its progress notification spinning after
+  the build: the message of the result (with its *Open folder* button) was awaited inside the
+  progress, so the progress ended only once the message was answered; the user saw a build that
+  never ended. Building the launchpad asks the floorplan of each application that has none, but
+  the prompt named only the entity set, not the application. The website served a `.vsix` built
+  from `main`, whose version (that of `packages/vscode/package.json`) was not the released one.
+- **Decision**: the progress covers the call of `rapt` only; the result is shown after it, without
+  being awaited. Every application of the VS Code workspace (each project with a service
+  definition) goes into the one launchpad of the workspace when the launchpad is built: they are
+  added to `launchpad.json` (what is there is kept) before the build; only an application built
+  alone (standalone) stays out of it. The choice reads "Launchpad of the workspace (3
+  applications)" with the names of the applications, never the name of a folder that could be
+  taken for one of them, and "<application> alone (standalone)". The floorplan prompt names the
+  application: the name of its workspace folder,
+  with the folder when they differ ("Helpdesk (Worklist) (helpdesk) — Ticket"); building the
+  launchpad still asks, application by application, the floorplan of every root entity set
+  without one (all of them when no application has a floorplan). The website serves the `.vsix`
+  of the latest GitHub release under its stable name, with its version shown on the page
+  (`%VSIX_VERSION%` of `scripts/build-site.mjs`); the Release workflow runs the Site workflow once
+  the release exists (a release created with the `GITHUB_TOKEN` does not trigger the `release`
+  event). Without a release, the `.vsix` is built from the commit. The website and the links of
+  the project follow the name of the repository, `Open-Rap-Runtime`.
+- **Tests**: `vscode/test/rapt.test.ts` (name of a project in the prompts, applications of the
+  workspace, URL of the feedback form); a launchpad of three projects (one already built, two without floorplan) under a folder
+  with an accent built by `rapt launchpad` in 2 s.
+
+## D73 — The missing abapGit files are written before a build in VS Code
+
+- **Context**: a project written by hand or by an AI agent can lack its abapGit files
+  (`.abapgit.xml`, the XML of the objects): `rapt build` does not need them, but the sources then
+  do not import into an SAP system with abapGit, which is the purpose of the project.
+- **Decision**: *Build the application* (standalone or launchpad) and *Build the launchpad* run
+  `rapt abapgit` on each application before building it: the missing files are written, the
+  existing ones are kept. The written files are listed in the log of the extension and announced
+  in a message; the objects that cannot be completed (a table without source) are logged; a
+  failure does not stop the build. The command line (`rapt build`, `rapt launchpad`) writes
+  nothing into the sources: in a terminal or a CI, `rapt abapgit` is run explicitly.
+- **Why**: the build of the extension is the moment the user hands the application over; the
+  sources that go with it must be importable as they are.
+- **Tests**: `vscode/test/rapt.test.ts` (missing files written, existing files kept, a second run
+  writes nothing).
+
+## D74 — The repository is public: feedback goes to its own issues
+
+- **Context**: the repository `ClementRingot/Open-RAP-Runtime` becomes public, so its issues are
+  open to the users; the separate feedback repository of D71 is no longer needed.
+- **Decision**: the feedback form of the website (and so the VS Code command *RAP: Report a bug
+  or request a feature…*) opens a pre-filled issue in the repository itself, with the same issue
+  forms, now in `.github/ISSUE_TEMPLATE` (bug report, feature request; blank issues disabled).
+  The npm packages give the repository and its issues (`repository`, `bugs`). The repository
+  `open-rap-runtime-feedback` points to the new place; its issues stay readable. The rest of D71
+  holds (fields filled from the query string, version and environment from the extension).
+- **Tests**: `compiler/test/docs.test.ts` (no link to the former name of the repository).

package/docs/FEATURES.md

@@ -284,4 +284,4 @@ dependent ETag, remote APIs.
 | MCP server of rapt for AI coding agents (`rapt agent`), registered in the agent mode of VS Code | ✅ | Check, objects, floorplans, abapGit, documentation (D64). |
 | npm package `open-rap-runtime` (`rapt`, `npx open-rap-runtime`) | ✅ | D65; archives of `pnpm pack` checked on each tag before publication with `NPM_TOKEN`. |
 | Website with the documentation | ✅ | D62, D63. |
-| Feedback form (website, *RAP: Report a bug or request a feature…*) to the public feedback repository | ✅ | D71. |
+| Feedback form (website, *RAP: Report a bug or request a feature…*) to the issues of the repository | ✅ | D71, D74. |

package/docs/README.md

@@ -117,9 +117,8 @@ Open RAP Runtime, contains this documentation and serves the `.vsix` of the late
 ## Feedback
 
 Report a bug or request a feature with the
-[feedback form](https://clementringot.github.io/RAP-Transpiler/feedback.html) (it opens a
-pre-filled issue in the public
-[feedback repository](https://github.com/ClementRingot/open-rap-runtime-feedback)), or in VS Code
+[feedback form](https://clementringot.github.io/Open-Rap-Runtime/feedback.html) (it opens a
+pre-filled issue in the [issues](https://github.com/ClementRingot/Open-RAP-Runtime/issues) of this repository), or in VS Code
 with *RAP: Report a bug or request a feature…*.
 
 ## Contributing

package/package.json

@@ -1,10 +1,18 @@
 {
   "name": "@open-rap/compiler",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Compiles SAP RAP sources (abapGit format) into a standalone Node.js OData V4 application.",
   "type": "module",
   "license": "MIT",
-  "homepage": "https://clementringot.github.io/RAP-Transpiler/",
+  "homepage": "https://clementringot.github.io/Open-Rap-Runtime/",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/ClementRingot/Open-RAP-Runtime.git",
+    "directory": "packages/compiler"
+  },
+  "bugs": {
+    "url": "https://github.com/ClementRingot/Open-RAP-Runtime/issues"
+  },
   "keywords": [
     "sap",
     "rap",
@@ -44,7 +52,7 @@
     "@abaplint/transpiler": "2.14.24",
     "chevrotain": "13.2.0",
     "fast-xml-parser": "5.12.0",
-    "@open-rap/model": "0.1.0"
+    "@open-rap/model": "0.1.2"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json && node scripts/copy-docs.mjs"