Add Asset category for API reference #6051
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've thought the same, and all *Handler's I believe belong to this section as well. The reason is that asset loading is a very separate thing while working with a resource - is a framework thing. e.g. AudioHandler - sounds like it is a class for handling sounds, but it is a handler for loading audio resources. |
slimbuck
approved these changes
Feb 14, 2024
|
@Maksims Yeah, handlers probably belong here too. I might do a follow up PR... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Separates out the
AssetAPI:I confirm I have read the contributing guidelines and signed the Contributor License Agreement.