Patrick Burrows

This is a dumb workaround, but it works: ``` try { app.UseAllElasticApm(_configuration); } catch (Exception ex) { // ignore this error } ``` You could, of course, make it more...

No, not really. I don't think that would work the same way (unless internally socket.io reuses the connection). The namespaces for socketio work more like this: class 1: ``` constructor()...

FWIW, I wound up just making my own copy of https://github.com/bougarfaoui/ng-socket-io/blob/master/socket-io.service.ts and adding support for specifying the namespace in the constructor. That's really all you need from this library, anyway.

``` constructor(namespace?: string) { let url: string = this.apiBase; if (namespace) { url += namespace; } const opts: SocketIOClient.ConnectOpts = {}; this.ioSocket = io(url, opts); } ``` Simply concatenates a...

Hey @Simbaclaws , I don't have that project current anymore. It's been awhile since I did this. :-) If you have it implemented already, go ahead and make a PR....

Actions seem to need a LOT more documentation. Apparently there are certain "magic" names you need to use for the names of actions? ("OutputExpression") and for the name of context...

If it matters, I updated to the LTS version of node and this still happens (20.12.2 as of the time I write this)

Keeping this alive. Still having to do this every single time you add a new dependency

I wound up using findText on the range object for the selected text, and storing the findIndex along with the serialization (so, if the selected text is "hello" and there...

Since this library is pretty dead, I wound up cloning the project here: https://github.com/pburrows/rangy-updated and publishing it in npm as rangy-updated. This clone accepts PRs. I might have solved the...