Serialize class entity to fbs

Author: melodyoncode

cpp/libclang/BUILD

@@ -39,6 +39,8 @@ rust_binary(
     deps = [
         "//cpp/libclang/src/utils",
         "//cpp/libclang/src/visitor:visit_tu",
+        "//tools/metamodel/class:class_diagram",
+        "//tools/serialization/flatbuffers/class:class_serializer",
         "@crates//:clang",
         "@crates//:clap",
         "@crates//:env_logger",

cpp/libclang/README.md

@@ -22,6 +22,7 @@ load("//cpp/libclang:cpp_parser.bzl", "cpp_parser")
 
 cpp_parser(
   name = "cpp_parser_include_3rdparty",
+  emit_debug_json = True,
   extra_args = [
   ],
   target = "//cpp/libclang/integration_test/cases/include_3rdparty",
@@ -32,11 +33,14 @@ cpp_parser(
 Where:
 
 - `target` is the Bazel target you want to parse.
+- `emit_debug_json` is optional and defaults to `False`. Enable it when you want the aggregated `debug.json` sidecar.
 
 Expected result:
 
 - Bazel creates parser output artifact:
-  - `bazel-bin/cpp/libclang/cpp_parser_include_3rdparty_result.json`
+  - `bazel-bin/cpp/libclang/cpp_parser_include_3rdparty_result.fbs.bin`
+- When `emit_debug_json = True`, the parser also writes:
+  - `bazel-bin/cpp/libclang/cpp_parser_include_3rdparty_result/debug.json`
 
 ## Configure debug logging
 
@@ -51,4 +55,6 @@ Accepted values are: `error`, `warn`, `info`, `debug`, `trace`.
 ## Quick check (optional)
 
 ```bash
-ls -l bazel-bin/cpp/libclang/cpp_parser_include_3rdparty_result.json
+ls -l bazel-bin/cpp/libclang/cpp_parser_include_3rdparty_result.fbs.bin
+ls -l bazel-bin/cpp/libclang/cpp_parser_include_3rdparty_result/debug.json
+```

cpp/libclang/cpp_parser.bzl

@@ -191,18 +191,21 @@ def _collect_required_llvm_include_args(cxx_builtin_include_files, extra_config_
     return result
 
 def _cpp_parser_impl(ctx):
-    output = ctx.actions.declare_file(
-        ctx.label.name + "_result.json",
+    output_dir = ctx.actions.declare_directory(
+        ctx.label.name + "_result",
     )
     libclang = ctx.file._libclang
 
     args = []
 
     args += [
-        "--output",
-        output.path,
+        "--output-dir",
+        output_dir.path,
     ]
 
+    if ctx.attr.emit_debug_json:
+        args.append("--json")
+
     target_compilation_flags_list = ctx.attr.target[CompilationFlagsInfo].flags.to_list()
 
     cxx_builtin_include_files = ctx.attr._llvm_cxx_builtin_include.files.to_list()
@@ -232,7 +235,7 @@ def _cpp_parser_impl(ctx):
 
     ctx.actions.run(
         inputs = inputs,
-        outputs = [output],
+        outputs = [output_dir],
         executable = ctx.executable.tool,
         tools = [ctx.attr.tool[DefaultInfo].files_to_run],
         arguments = args,
@@ -249,7 +252,8 @@ def _cpp_parser_impl(ctx):
     )
 
     return DefaultInfo(
-        files = depset([output]),
+        files = depset([output_dir]),
+        runfiles = ctx.runfiles(files = [output_dir]),
     )
 
 cpp_parser = rule(
@@ -267,6 +271,10 @@ cpp_parser = rule(
         "extra_args": attr.string_list(
             default = [],
         ),
+        "emit_debug_json": attr.bool(
+            default = False,
+            doc = "Emit debug.json alongside the FlatBuffer output. Intended for tests/debugging.",
+        ),
         "_libclang": attr.label(
             allow_single_file = True,
             default = "@llvm_toolchain_llvm//:lib/libclang.so",

cpp/libclang/integration_test/README.md

@@ -18,13 +18,14 @@ This directory contains integration tests for the C++ libclang parser and relate
 ## Directory Structure
 
 - `cases/`: Each subdirectory is an independent test case, containing C++ sources, BUILD files, and golden `expected.json` outputs.
-- `test_framework.rs`: Rust test framework that invokes the parser and compares output to the golden file.
+- `test_framework.rs`: Rust test framework that invokes the parser and compares the debug JSON sidecar to the golden file.
 - `BUILD`: Bazel build and test rules for integration.
 
 ## Test Workflow
 
 1. Each case directory contains C++ source files, headers, a BUILD file, and an `expected.json` golden output.
-3. The Rust test framework uses the parser to process the case and compares the output to `expected.json`.
+2. The case `cpp_parser(...)` target must set `emit_debug_json = True` so the parser emits the aggregated `debug.json` sidecar required by the test harness.
+3. The Rust test framework reads `debug.json` from the parser output directory and compares it to `expected.json`.
 4. To batch test all cases:
 
 ```bash

cpp/libclang/integration_test/cases/complex_class/BUILD

@@ -28,6 +28,7 @@ cc_library(
 
 cpp_parser(
     name = "parser",
+    emit_debug_json = True,
     extra_args = [
     ],
     target = ":complex_class",

cpp/libclang/integration_test/cases/complex_class/expected.json

@@ -1,5 +1,5 @@
 {
-  "classes": {
+  "types": {
     "MyNamespace::MyNamespace2::Car": {
       "id": "MyNamespace::MyNamespace2::Car",
       "name": "Car",

cpp/libclang/integration_test/cases/include_3rdparty/BUILD

@@ -31,6 +31,7 @@ cc_library(
 
 cpp_parser(
     name = "parser",
+    emit_debug_json = True,
     extra_args = [
     ],
     target = ":include_3rdparty",

cpp/libclang/integration_test/cases/include_3rdparty/expected.json

@@ -1,5 +1,5 @@
 {
-  "classes": {
+  "types": {
     "Car": {
       "id": "Car",
       "name": "Car",

cpp/libclang/integration_test/cases/method_parameter_type/BUILD

@@ -27,6 +27,7 @@ cc_library(
 
 cpp_parser(
     name = "parser",
+    emit_debug_json = True,
     extra_args = [],
     target = ":method_parameter_type",
     tool = "//cpp/libclang:clang_rs_parser",

cpp/libclang/integration_test/cases/method_parameter_type/expected.json

@@ -1,5 +1,5 @@
 {
-  "classes": {
+  "types": {
     "MethodParameterTypeSample": {
       "id": "MethodParameterTypeSample",
       "name": "MethodParameterTypeSample",