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
I really like this library concept, and I fully agree with the outlined issue described in the philosophy part. But one thing I think would be a great enhancement would be to be able to define different events which ipcMain and ipcRenderer can send.
I saw that another typings library had that feature, so I forked this and tried to tinker it myself but my understanding of how to work with these types isn't enough.
Basically, I think it'd be helpful to do:
interfaceEventsFromMain{'msg-A': void;}interfaceEventsFromRenderer{'msg-B': void;}/* First generic indicates what types can be used for send methods, second generic indicates what can be used in listener methods */constipcRenderer: StrictIpcRenderer<EventsFromRenderer,EventsFromMain>=electron.ipcRenderer;constipcMain: StrictIpcMain<EventsFromMain,EventsFromRenderer>=electron.ipcMain;
The text was updated successfully, but these errors were encountered:
I really like this library concept, and I fully agree with the outlined issue described in the philosophy part. But one thing I think would be a great enhancement would be to be able to define different events which ipcMain and ipcRenderer can send.
I saw that another typings library had that feature, so I forked this and tried to tinker it myself but my understanding of how to work with these types isn't enough.
Basically, I think it'd be helpful to do:
The text was updated successfully, but these errors were encountered: