Option inside Bundle struct complains about trait bounds | Bevy | Page 1

stray harbor Dec 29, 2023, 11:50 PM

#

Hi, I've got a Bundle containing an Option<Clickable> where Clickable is an enum that derives Component. The compiler is complaining about Option<Clickable> not implementing Component. I had the same issue when I was trying to query Option<Clickable>, but this was mitigated by simply referencing Clickable (so Option<&Clickable>. I feel like creating a wrapper type for this isn't the best way around this (and wouldn't it have the same issue?), so does anyone have any tips?

vagrant basalt Dec 29, 2023, 11:53 PM

#

What would a bundle with a Option type do?

#

insert nothing if its None?

stray harbor Dec 29, 2023, 11:53 PM

#

Yep

#

Previously I had a Nothing inside the enum but it felt redundant so I'm trying the Option route

vagrant basalt Dec 29, 2023, 11:54 PM

#

i dont think thats implemente

#

in fact

#

https://github.com/bevyengine/bevy/issues/2157

GitHub

Bundles with optional components · Issue #2157 · bevyengine/bevy

What problem does this solve or what need does it fill? Currently if a bundle has components which are wrapped in an Option<>, they are treated literally. However in my opinion it would be a ...

#

its a open issue

stray harbor Dec 29, 2023, 11:55 PM

#

Woah google

stray harbor Dec 29, 2023, 11:57 PM

#

vagrant basalt i dont think thats implemente

So after skiming the issue, should I stick with my previous method of having Clickable::Nothing?

wooden grail Dec 30, 2023, 1:53 AM

#

@stray harbor fwiw for things like this.. I add/remove components as necessary. So either it's clickable or it isn't and it isn't clickable if the component is removed.

stray harbor Dec 30, 2023, 1:54 AM

#

...i don't know why i didn't think of this LOL

#

ill do that, that makes a lot more sense

#Option inside Bundle struct complains about trait bounds