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.

Sign up for GitHub

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

Adding derive Reflect for tick structs #11641

Merged
merged 6 commits into from
Feb 1, 2024
Merged

Adding derive Reflect for tick structs #11641

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ac6ede3
derive Reflect for tick structs
cbournhonesque-sc Feb 1, 2024
f03ee11
add more reflects
cbournhonesque-sc Feb 1, 2024
ee686a1
fmt
cbournhonesque-sc Feb 1, 2024
98eb828
add reflect attribute
cbournhonesque-sc Feb 1, 2024
63151fc
register the types
cbournhonesque-sc Feb 1, 2024
97bcad0
feature gate reflect derives
cbournhonesque-sc Feb 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
add reflect attribute
  • Loading branch information
@cbournhonesque-sc
cbournhonesque-sc committed Feb 1, 2024
commit 98eb828cad87cf19bab9fb7a450277baf02f1ffd
3 changes: 3 additions & 0 deletions crates/bevy_ecs/src/component.rs
View file
Open in desktop
Copy link
Member

@MrGVSV MrGVSV Feb 1, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably also register these types into the App (although I’m not sure if the bevy_ecs has a plugin or anything that would make sense to hold that logic)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, there's no great spot to do this. Maybe bevy_core?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added them in bevy core, seems like a good place for it

Original file line number Diff line number Diff line change
Expand Up @@ -288,6 +288,7 @@ impl ComponentInfo {
/// from a `World` using [`World::component_id()`] or via [`Components::component_id()`]. Access
/// to the `ComponentId` for a [`Resource`] is available via [`Components::resource_id()`].
#[derive(Debug, Copy, Clone, Hash, Ord, PartialOrd, Eq, PartialEq, Reflect)]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also add the appropriate registrations (e.g. #[reflect(Hash, PartialEq)])?

Same for the other items.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, should i add Clone as well?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think there is one for Clone 🤔

#[reflect(Debug, Hash, PartialEq)]
pub struct ComponentId(usize);

impl ComponentId {
Expand Down Expand Up @@ -671,6 +672,7 @@ impl Components {
/// A value that tracks when a system ran relative to other systems.
/// This is used to power change detection.
#[derive(Copy, Clone, Debug, Eq, PartialEq, Reflect)]
#[reflect(Debug, PartialEq)]
pub struct Tick {
tick: u32,
}
Expand Down Expand Up @@ -764,6 +766,7 @@ impl<'a> TickCells<'a> {

/// Records when a component was added and when it was last mutably dereferenced (or added).
#[derive(Copy, Clone, Debug, Reflect)]
#[reflect(Debug)]
pub struct ComponentTicks {
pub(crate) added: Tick,
pub(crate) changed: Tick,
Expand Down