You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My colleagues find it unclear to tell what MyBox's extension methods actually do, and when they go to the documentation, it's not much help either. I understand that extension documentation is still a while away, but I thought: with very few lines added, the wiki page for Extensions can instruct users to enable self-documentation in Intellisense, since Unity does not do this by default. I propose something like this appended to the current Extensions wiki page:
In the mean time, you can enable Intellisense to display self-documentation of these methods by following these steps: In Unity Editor, open Edit > Preferences > External Tools and enable "Generate .csproj files for" Registry packages and Git packages, then click "Regenerate project files". The next time you open Visual Studio, Intellisense will show you comments for MyBox's extension methods.
The text was updated successfully, but these errors were encountered:
This was actually an issue that was raised over at Unity Forum, which I chimed in to support for an engine-level fix. But seeing how this is very low on the critical scale for Unity, we'll just have to pass around awareness of this workaround.
My colleagues find it unclear to tell what MyBox's extension methods actually do, and when they go to the documentation, it's not much help either. I understand that extension documentation is still a while away, but I thought: with very few lines added, the wiki page for Extensions can instruct users to enable self-documentation in Intellisense, since Unity does not do this by default. I propose something like this appended to the current Extensions wiki page:
The text was updated successfully, but these errors were encountered: