[Feature] Sequence reuse

[not-elm]

This issue is about a new feature proposed from below.

• Better Big O #7

Below is a quote from the PR.

---

Future Idea

One idea to consider for the future is making the key sequence that was pressed available somehow. Maybe something simple like this:

#[derive(Resource)]
struct LastKeySequence(Option<Vec<KeyChord>>)

But maybe that's too simple. What'd be best is if we could optionally pass the key sequence to the system we're invoking. But I don't really know how to do that.

[shanecelis]

I suggested this feature, but I ended up implementing this in bevy_minibuffer without needing any special handling by bevy-input-sequence. What I did was when I registered my key sequence on the action, I simply registered the set key sequence to a resource.

So I'm all for keeping this crate simpler when possible. I'd be happy to close this issue.