The Unity 2019.4 Scripting API documentation page for the Transform class here: It will also help me provide better feedback to Unity about bugs or feature requests, and avoid unnecessary support requests that question limitations or bugs in the Unity C# implementation, requiring a Unity Tech QA specialist to inspect the C# source or consult a Unity Tech developer for clarification."
"As a developer, when browsing the Unity Scripting API docs, I would like be able to view a particular class or method, and then click on a link that jumps directly to the C# reference code where that class or method is defined, to better understand how it works, how to use it, or reimplement its functionality if needed due to limitations or bugs. Here's an agile / scrum style user story: This could also be done for the packages documentation. If you want to go a step further to enable Unity developers with excellent documentation workflows: integrate or link to the Unity C# reference directly in the Unity's Scripting API documentation. NET assemblies into C# (legally) and redistributing them (illegally) without any of the helpful variable names and comments.Įxpectation set in Unity Blog post, March 2018: Not doing so will end up resulting (and likely already has resulted) in the same problem this repo was created to eliminate: people disassembling the Unity. Will you or do us a huge favor and spare a moment to forward this to the appropriate team / product manager, or someone that knows more? Or maybe knows who owns this or knows someone that could own this? ( as Ali was so kind to spearhead managing similar, possibly related challenges with Unity Graphics repo.) It would be greatly appreciated. The original Unity blog announcement post authored by in 2018 states " C# reference source code is released under a license which only permits you to read the code, not modify it." (unlike other published Unity source repos) and that it was released in part to let us see " the original comments and variable names" (self documenting code / internal documentation made external since it is not distributed with the Editor in readable form) and "for the purpose of understanding or improving your projects made with Unity." (aligned with the purpose of the Scripting API documentation.)
Where the Unity Scripting API documentation ends, the Unity C# Reference begins. While it's apparently not managed by the documentation team (or anyone at the moment,) this is a rather special repo that seems to fall in a grey area. It's a request to update a reference that we as developers, rely on as a form of documentation similar to and in close conjunction with the Scripting API docs in real world workflows.
Click to expand.Possibly, but unlike the posts in that section -this is not a technical question about Scripting.
0 kommentar(er)
