Add support for generating class reference descriptions from C# documentation comments
### Describe the project you are working on Currently working on a movement shooter, but this applies to _any_ project using C#. ### Describe the problem or limitation you are having in your project C# docstrings do not apply to inspector property documentation-on-hover, unlike [GDScript documentation comments](https://docs.godotengine.org/en/stable/tutorials/scripting/gdscript/gdscript_documentation_comments.html). ### Describe the feature / enhancement and how it helps to overcome the problem or limitation Seeing docstrings in the inspector is valuable for both solo devs, and particularly for teams, where nontechnical team members often need to interact with classes generated by programmers, and the name of a property alone may not fully describe its functionality. ### Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams While I'm unclear on the implementation details, the end-goal is fairly straightforward- Bring C# documentation comments to feature parity with GDScript documentation comments. ### If this enhancement will not be used often, can it be worked around with a few lines of script? Not that I'm aware of. ### Is there a reason why this should be core and not an add-on in the asset library? For the same reason that both C# and GDScript documentation comments are core.
Posted by Mantissa-23 on Oct 27, 2023, 2:30 AM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
Add support for generating class reference descriptions from C# documentation comments
### Describe the project you are working on Currently working on a movement shooter, but this applies to _any_ project using C#. ### Describe the problem or limitation you are having in your project C# docstrings do not apply to inspector property documentation-on-hover, unlike [GDScript documentation comments](https://docs.godotengine.org/en/stable/tutorials/scripting/gdscript/gdscript_documentation_comments.html). ### Describe the feature / enhancement and how it helps to overcome the problem or limitation Seeing docstrings in the inspector is valuable for both solo devs, and particularly for teams, where nontechnical team members often need to interact with classes generated by programmers, and the name of a property alone may not fully describe its functionality. ### Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams While I'm unclear on the implementation details, the end-goal is fairly straightforward- Bring C# documentation comments to feature parity with GDScript documentation comments. ### If this enhancement will not be used often, can it be worked around with a few lines of script? Not that I'm aware of. ### Is there a reason why this should be core and not an add-on in the asset library? For the same reason that both C# and GDScript documentation comments are core.
Comments (0)
No comments yet. Start the discussion.