You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the LeagueClient class with the client already running, connect event doesn't fire.
With the app running I have to shutdown the client and reopen it for the event to fire.
I am just wondering if this is the default behavior or am I missing something here.
Note:
I am using the library as an external library in electron-builder config, not doing so will throw an error about riotgames.pem location. So by setting the package as a native dependency it solves the issue or I can copy the file to my project directory, but I don't think that's the issue here.
I am using the example code from the documentation
I suppose it'd be correct to say this is the default/expected behavior. Maybe it would be better to rename the event to 'reconnect' at next major version... It's basically an event for when the client is restarted (see source https://github.com/matsjla/league-connect/blob/master/src/client.ts#L73)
As of right now (see #55 for wanted feature) you have to have a set of credentials to construct the LeagueClient class, which already indicates you have received credentials from a running client.
When using the
LeagueClient
class with the client already running,connect
event doesn't fire.With the app running I have to shutdown the client and reopen it for the event to fire.
I am just wondering if this is the default behavior or am I missing something here.
Package Version: v5.3.1
Environment: Vue CLI Plugin Electron Builder
Node: v16.14
Electron: v13
Note:
I am using the library as an external library in
electron-builder
config, not doing so will throw an error aboutriotgames.pem
location. So by setting the package as a native dependency it solves the issue or I can copy the file to my project directory, but I don't think that's the issue here.I am using the example code from the documentation
The text was updated successfully, but these errors were encountered: