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
It's likely happening because this file is generated (filename generated.rs) and part of the target folder. It's also not checked into version control. Maybe moving it to a gen/ folder inside src could help.
The text was updated successfully, but these errors were encountered:
Question: is the generated source code ever going to be actually useful for end users? I'm aware that some were led to believe that the methods don't exist because they can't follow the source link, but perhaps it's better to approach this from a documentation perspective, than to try and fight with rustdoc and complicate the build process?
We can, for example, emit a short notice like:
Note: Generated source code for API methods might not be availble in rustdoc. This is normal.
... for each of the methods. I recall there being some way to detect whether the program is being compiled for docs.rs, which can optionally be used to reduce clutter when the docs are being built locally.
For symbols inside
gdnative::api
module, navigating to the source code leads to an error.In gdnative 0.10.1:
KinematicBody::move_and_slide
, then click[source]
This was already present in 0.9.0:
KinematicBody::move_and_slide
, then click[src]
Result:
It's likely happening because this file is generated (filename
generated.rs
) and part of thetarget
folder. It's also not checked into version control. Maybe moving it to agen/
folder insidesrc
could help.The text was updated successfully, but these errors were encountered: