Skip to content

Provide more sugar API on ResourceManager #2806

@MrKou47

Description

@MrKou47

Is your feature request related to a problem? Please describe.
Currently, when a user wants to get the resource instance, they can only use the resourceManager.load API to do this job. Sometimes that is not convenient and easy to make mistakes, especially when the resource path includes specific characters like Chinese, emojis, or spaces, etc.

Describe the solution you'd like

Due to having an Online Editor, providing a ResourceManager.getResourceById() API seems more reasonable and easy to implement.

Additional context
We also need to consider providing ResourceManager.getResourceByPath() as a sugar API for ResourceManager.load, which semantics look suitable in that case.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions