Skip to content

Conversation

@bdovaz
Copy link

@bdovaz bdovaz commented Sep 27, 2025

I've done a lot of things, you can really see it in the README.md file in the Advanced usage section.

If you're still interested in maintaining this project (I hope you are), I'll add you as the owner of the NuGet package.

Highlights:

  • Stop hardcoding as much as possible and make it parameterizable so that it is compatible even with Unity packages and not just with the editor.
  • Project converted to cli distributed in NuGet as a cross platform dotnet tool.
  • There is a main command that generates the xrefmap file.
  • There is a test command that, when passed an xrefmap file, allows you to test the links in the href field.
  • Test the cli commands.
  • Patch a few more cases with string replace so that it generates the documentation correctly.

I haven't fixed the github pages workflow in this PR (it's been failing since November 2024) with the new changes because, at the very least, this PR dotnet/docfx#10827 that I created due to a problem that occurs when trying to generate the UnityEngine xrefmap needs to be merged.

@bdovaz bdovaz changed the title Major improvements feat: major improvements Sep 27, 2025
@bdovaz
Copy link
Author

bdovaz commented Oct 3, 2025

@NormandErwan ping!

@NormandErwan
Copy link
Owner

Hello, and thank you very much for this PR. I quickly looked over the changes, and they seem to be a very good improvement!

I have very little time these days, but I will do my best to merge them.

Thank you for your proposal regarding the NuGet package. However, it is your work, so I would prefer you to remain the owner.

@bdovaz
Copy link
Author

bdovaz commented Oct 9, 2025

Thank you for your proposal regarding the NuGet package. However, it is your work, so I would prefer you to remain the owner.

Maybe I didn't explain myself well. What I mean is that in NuGet, packages can have N owners.

And since the GitHub Actions workflow publishes the package, you should configure the related secrets in your repository. Because right now it's published from my fork.

image

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.

2 participants