Skip to content
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

Add TypePath to the prelude #9963

Merged
merged 1 commit into from
Sep 29, 2023

Conversation

ItsDoot
Copy link
Contributor

@ItsDoot ItsDoot commented Sep 29, 2023

Objective

In order to derive Assets (v2), TypePath must also be implemented. TypePath is not currently in the prelude, but given it is required when deriving something that is in the prelude, I think it deserves to be added.

Solution

Add TypePath to bevy_reflect::prelude.

@alice-i-cecile alice-i-cecile added C-Usability A targeted quality-of-life change that makes Bevy easier to use A-Reflection Runtime information about types labels Sep 29, 2023
@MrGVSV MrGVSV added the S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it label Sep 29, 2023
@alice-i-cecile alice-i-cecile added this pull request to the merge queue Sep 29, 2023
Merged via the queue into bevyengine:main with commit f8fd93f Sep 29, 2023
@ItsDoot ItsDoot deleted the feat/typepath-prelude branch September 29, 2023 16:06
rdrpenguin04 pushed a commit to rdrpenguin04/bevy that referenced this pull request Jan 9, 2024
# Objective

In order to derive `Asset`s (v2), `TypePath` must also be implemented.
`TypePath` is not currently in the prelude, but given it is *required*
when deriving something that *is* in the prelude, I think it deserves to
be added.

## Solution

Add `TypePath` to `bevy_reflect::prelude`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Reflection Runtime information about types C-Usability A targeted quality-of-life change that makes Bevy easier to use S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants