expose the statsdclient to the request

[designfrontier]

This would facilitate users doing custom statsd stuff and building out there own stats for performance metrics etc.

The statsd client already exists in the router.js file and in the correct scope to be added to the connection object passed to route events. Just needs to be added.

[cursiv3]

Hi I've been looking for a project to get into open source, I think I could handle this. If I'm understanding correctly, you would simply like statsdClient added inside the connection object so it can be accessed in a monument project route file events callback like events.statsdClient?

[designfrontier]

Yeah!

As I am thinking about this more it might actually be best to just expose it at the same level as the events object. That way you could do require('monument').statsd to get it wherever you want to use it. Alternately if that ends up not being feasible you could just add it to the connection object in the router so that it is available to all routes.

[cursiv3]

I submitted a PR that allows access to statsd anywhere via require('monument').statsd:
#577

but as I commented there, I couldn't figure out how to test it

[designfrontier]

Line 96-108 of index.test.js are a pretty simple approach to testing this.

Basically assert that the statsd client is returned on the app. The rest of the tests around statsd are already there so testing it in that location isn't needed.

[cursiv3]

Will do! And thanks for the heads up on the test stuff, I should have poked around in there more

[KazChe]

Did this change make it?