Californ1a

>Also, we don't need to stick to the existing events only, we could add before events too, like beforecardplay, and always send a game instance to the event. It would...

>I think this eventloader pattern is a lot confusing - never seen it. Do you have any resource about it? There isn't really any specific documentation I can find on...

Definitely optional. Personally I see it less as confusing and more like if I intentionally click skip on any manual skip segment, then that's me essentially telling the extension I...

I would have just sent a PR since the first one is a simple class rename, but I don't know how to fix the second issue.

Yes, it is working in PR #3295. It just hasn't been merged yet.

> As for your other issue, simply append `Connector.onReady = Connector.onStateChanged;` to the end of the connector, and it should work. Thanks, that did it. Edit: I also found one...

Would it be bad practice to hijack the react app's internal state? Replacing this: ```js Connector.playButtonSelector = 'button[title="Play"]'; ``` with ```js Connector.isPlaying = () => { return document.querySelector("#root")._reactRootContainer._internalRoot.current.memoizedState.element.props.store.getState().player.isPlaying; } ```...

As it turns out, `_reactRootContainer` isn't actually accessible from within the context of the content script, only within the page itself. So instead, I've just added a selector for the...

Is there something blocking this from being merged? I thought it was done 2 months ago.

I was super confused for a few minutes when I first imported my wakatime data because of this. Made me think it only imported one day's worth of stats since...