-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve clarity of existing bevy_assets documentation #17830
base: main
Are you sure you want to change the base?
Conversation
@@ -5,6 +5,8 @@ use bevy_reflect::TypePath; | |||
|
|||
/// A "loaded folder" containing handles for all assets stored in a given [`AssetPath`]. | |||
/// | |||
/// This is produced by [`AssetServer::load_folder`](crate::prelude::AssetServer::load_folder). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For my own learning, do these links work? I thought you either need it to guess it automatically or there's a "symbol" section in another paragraph.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These inline links are the third way :) These vs new-line links are just a matter of style.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Objective
While surveying the state of documentation for bevy_assets, I noticed a few minor issues.
Solution
Revise the docs to focus on clear explanations of core ideas and cross-linking related objects.