Skip to content

fix: replace the XML generator with a reflection-based one#1151

Open
gennaroprota wants to merge 7 commits intocppalliance:developfrom
gennaroprota:develop
Open

fix: replace the XML generator with a reflection-based one#1151
gennaroprota wants to merge 7 commits intocppalliance:developfrom
gennaroprota:develop

Conversation

@gennaroprota
Copy link
Collaborator

@alandefreitas: Please let me know what you think and... if I have commented it too much :-).

@github-actions
Copy link

github-actions bot commented Jan 21, 2026

🚧 Danger.js checks for MrDocs are experimental; expect some rough edges while we tune the rules.

ℹ️ Info

Note

Commit 7b094ae (fix: replace the XML generator with a reflection-based one) touches 2512 source lines (non-test). Large change; add reviewer context if needed.

✨ Highlights

  • 🧪 Existing golden tests changed (behavior likely shifted)

🧾 Changes by Scope

Scope Lines Δ Lines + Lines - Files Δ Files + Files ~ Files ↔ Files -
🥇 Golden Tests 45492 36338 9154 243 12 231 - -
🛠️ Source 2533 839 1694 10 1 7 - 2
🏗️ Build / Toolchain 1135 781 354 2 - 2 - -
⚙️ CI 52 37 15 1 - 1 - -
📦 Other 6 6 - 1 - 1 - -
Total 49218 38001 11217 257 13 242 - 2

Legend: Files + (added), Files ~ (modified), Files ↔ (renamed), Files - (removed)

🔝 Top Files

  • test-files/golden-tests/javadoc/ref/ref.xml (Golden Tests): 2765 lines Δ (+2182 / -583)
  • test-files/golden-tests/config/auto-function-metadata/returns-from-special.xml (Golden Tests): 2613 lines Δ (+1936 / -677)
  • test-files/golden-tests/javadoc/copydoc/param-types.xml (Golden Tests): 2243 lines Δ (+1768 / -475)

Generated by 🚫 dangerJS against 306c09f

@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://1151.mrdocs.prtest2.cppalliance.org/index.html

If more commits are pushed to the pull request, the docs will rebuild at the same URL.

2026-01-21 17:01:42 UTC

@alandefreitas
Copy link
Collaborator

I think we should be removing way more code than including for this PR to make sense. The test outputs haven't even changed. This should be a bug fix, not a refactor. The biggest problem with this generator is that it's not in sync with the metadata. And the reason this generator is out of sync is that we didn't have reflection, and manually keeping it in sync was too expensive and fragile. So what we want to do is let reflection handle the whole thing, and the whole generator will have only one or two functions that recursively iterate over everything to generate the metadata. 🥳

This means the XML outputs will change completely, as they now reflect everything in the metadata, which is what this generator was meant for. Our intention is not to recreate the broken version, but to recreate it with reflection. If we don't fix it, reflection would mean more code rather than less, as we now have to force reflection to recreate the errors we had without it (which is even harder than just keeping the original errors). And that's going to be extra code just to maintain it broken.

I think another issue here is that we should probably address the other issue first, where we should remove those small workarounds from reflection to make it reflect into different key names. Only canonical names should be used. All generators should have access to the same fields with the same names. Making this happen is basically just the finalization of the previous issue we already merged. And maybe the @meta field is required to make that happen, since ambiguity might arise. Only after establishing the canonical field names can we use them to generate XML. 😅

@alandefreitas
Copy link
Collaborator

What happened to this PR? I thought it would become more active after #1153 🚀

@gennaroprota
Copy link
Collaborator Author

gennaroprota commented Jan 29, 2026

I removed the commit before pulling, after merging #1153, and GitHub closed it. I shouldn't have used the develop branch.

@alandefreitas
Copy link
Collaborator

Oh 😅

@gennaroprota gennaroprota reopened this Feb 2, 2026
@gennaroprota gennaroprota changed the title refactor: leverage reflection in the XML generator fix: leverage reflection in the XML generator Feb 2, 2026
@gennaroprota gennaroprota marked this pull request as draft February 2, 2026 17:57
@gennaroprota gennaroprota changed the title fix: leverage reflection in the XML generator fix: replace the XML generator with a reflection-based one Feb 2, 2026
@codecov
Copy link

codecov bot commented Feb 18, 2026

Codecov Report

❌ Patch coverage is 93.10345% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 77.02%. Comparing base (a1f9a82) to head (306c09f).

Files with missing lines Patch % Lines
src/lib/Gen/xml/XMLWriter.cpp 92.68% 0 Missing and 6 partials ⚠️
src/lib/AST/ExtractDocComment.cpp 93.75% 0 Missing and 1 partial ⚠️
src/lib/Support/Reflection/ReadableTypeName.hpp 92.85% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1151      +/-   ##
===========================================
+ Coverage    76.38%   77.02%   +0.64%     
===========================================
  Files          311      310       -1     
  Lines        29672    28974     -698     
  Branches      5863     5781      -82     
===========================================
- Hits         22664    22318     -346     
+ Misses        4735     4429     -306     
+ Partials      2273     2227      -46     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gennaroprota gennaroprota force-pushed the develop branch 11 times, most recently from 2ac16d5 to 0312652 Compare February 24, 2026 15:52
This fixes the XML generator, which was out of sync with our metadata,
by replacing it with a reflection-based implementation. The XML output
structure changes completely, but contains equivalent information.
Reason: See the new code comment in codecov.yml.
This adds support for all five admonition types, with corresponding
tests, plus tests for type-based friend declarations and pointers to
members.
@gennaroprota gennaroprota marked this pull request as ready for review February 24, 2026 17:48
@cppalliance-bot
Copy link

cppalliance-bot commented Feb 24, 2026

An automated preview of the documentation is available at https://1151.mrdocs.prtest2.cppalliance.org/index.html

If more commits are pushed to the pull request, the docs will rebuild at the same URL.

2026-02-27 16:27:09 UTC

@gennaroprota gennaroprota force-pushed the develop branch 9 times, most recently from 4b8a263 to 4012496 Compare February 26, 2026 11:20
This adds an `is-bottleneck` matrix flag for the following
configurations:

- Any compiler with MSan
- Apple Clang + ASan
- Apple Clang + UBSan

and, for these entries, skips the AsciiDoc/HTML golden tests and
self-doc test while still running all the other tests.

This reduces the wall-clock time of the overall CI run by removing the
heaviest tests.
@gennaroprota gennaroprota force-pushed the develop branch 2 times, most recently from 0338acf to e4510f8 Compare February 27, 2026 08:31
On pull_request, only generate the AsciiDoc format (the one that goes to
the website after Asciidoctor rendering). The XML and HTML formats are
skipped because they are never published from a PR.
Demo generation previously swallowed failures silently due to the
absence of `set -e`. Each demo now checks its exit code: failures remove
partial output, and the full list with reproduction commands is reported
at the end of the step.
The remote documentation step fetches and builds develop, master, and
all tags. This content is unrelated to the PR and is only needed for
website publishing.

The local documentation step (which builds only HEAD) still runs and
validates that the PR does not break doc generation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants