Carter Anderson

Bevy used to render text using [skribo](https://github.com/linebender/skribo), which in turn depends on font-kit. I explicitly moved off of it because it rendered the same fonts differently on different platforms (because...

I was able to add this in the derive macro by adding a `#[doc = ""]` attribute to the `Component` impl. Obviously not _ideal_ because its not directly on the...

This has been posted! https://bevyengine.org/news/community-reflection-on-bevys-fourth-year/

Rather than implement a new "query style" API, we could also consider: ```rust #[derive(Event)] struct Foo { foo: i32 } #[derive(Event)] struct Bar { bar: bool } #[derive(Event)] enum Combined...

Notably, this would require essentially no changes. Just an implementation of the `trigger_map` observer system, which would watch for the wrapped type and trigger the Combined enum type.

Just put together a PR for consideration, given how simple this was to implement.

Before we go too deep down this rabbit hole, can we discuss actual use cases? It would be good to come up with some real-world scenarios to illustrate why this...

I think we should prioritize adding support for this. To make this generically usable (especially in cases like UI), I think we'd need to support writing an observer that accepts...

Hmmm yeah libraries shouldn't check in cargo.lock as that makes coordination across contexts like this impossible. I'm not familiar with the issue that resulted in you needing to check it...

Ah I just got educated on https://blog.rust-lang.org/2023/08/29/committing-lockfiles.html and have been told that this does not affect downstream consumers. So I guess I don't care if you keep or remove it...