Mikkel Rasmussen

I implemented ci caching for crates db, so it only fetches the zip after 24 hours, which fits the timestamp for when the zip file gets updated by new data:...

> Also, surprisingly, this is way slower than the network call to github. I would have assumed, since it's a local db it would be pretty quick. I guess there's...

I think its properly a good idea to have a notice about dbdump size and instructions if users want to run the generate-assets locally, something like https://github.com/IceSentry/bevy-website/pull/3

The caching should also have to be added to `.github/workflows/deploy.yml`, though I don't know if they are going to share the cache, ideally, they should.

That's because `get_crate` uses `rev_dependency` 😅 `get_crate` combines all query to get the full crate and its reverse dependencies as you get on [crates.io](https://crates.io/crates/bevy_config_cam/0.3.0/dependencies). Also, I think my naming of...

Related #379

I'm first available after the 20th of August, so it depends on the release plan for me.

Also, which might (or might not) be the reason for some of your other issues, because of the new executor, your library has some system order ambiguities. You can ignore...

Another thing that might be worth looking into. I can see that you're using the heap to store the keycode input (Box). Which shouldn't have any major impact on performance...

Hi @tesfabpel :wave: Keybindings have already been discussed in [this issue (#7) ](https://github.com/sburris0/bevy_flycam/issues/7#issuecomment-826261751) and was deemed to add too much complexity to the project. That is of course unless @sburris0...