@open-rap/compiler 0.1.1 → 0.1.2

package/docs/DECISIONS.md

@@ -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,
@@ -1552,3 +1554,31 @@ correspond to points 1 to 13 of §11 of PLAN.md. The milestones M1 to M6 are tho
 - **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

@@ -118,8 +118,7 @@ Open RAP Runtime, contains this documentation and serves the `.vsix` of the late
 
 Report a bug or request a feature with the
 [feedback form](https://clementringot.github.io/Open-Rap-Runtime/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
+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.1",
+  "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/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.1"
+    "@open-rap/model": "0.1.2"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json && node scripts/copy-docs.mjs"