Development/Test Mode about analytics-ruby HOT 5 CLOSED

@travisjeffery I'm assuming you can enable request stubbing by passing:

Analytics.init({ stub: true, ... })

Correct? Any chance you could add a bit of documentation on Analytics#initialize?

It's a little odd that the setup process isn't documented in the README. I can submit a PR if you folks need some help getting that into shape.

from analytics-ruby.

@olivierlacan :stub is documented at the bottom of our dedicated docs page, which is linked on the readme. go here: https://segment.io/docs/libraries/ruby/ and scroll to the bottom. i'll add a section title for that bit, thanks for bringing this up. all the options are documented there.

stub's available in v2, which is namespaced and not a singleton. so you would do:

Analytics = Segment::Analytics.new(stub: true)

from analytics-ruby.

Yeah, that makes some sense. I definitely want to have more logging in the library everywhere which can be enabled, so big +1 on logging requests there, though I'm not sure if I'm sold on the DI route yet.

FWIW: what we do currently is set up a "development" project and then use a separate key for prod vs dev setups. We then look at requests going into the segment.io debugger when figuring out what is being sent.

@travisjeffery

from analytics-ruby.

ok you'll be able to stub requests when that's pushed, i'm not sold on di in ruby either. http://david.heinemeierhansson.com/2012/dependency-injection-is-not-a-virtue.html

from analytics-ruby.

Thanks! I'm not going to argue about DI or not even though it would add more extensibility.
This solves testing/dev mode issue so thank you very much!

from analytics-ruby.