add mock.js

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?

[stephenmathieson]

This patch adds a mock.js file, which we'll be able to use in
development/test/etc (anywhere you don't want to send real events).

I'm envisioning usage looking something like:

const{NODE_ENV='development'}=process.envconstAnalytics=NODE_ENV==='production'
? require('analytics-node')
: require('analytics-node/mock')constanalytics=newAnalytics('abc write key',{some: 'options'})analytics.track({userId: 'aaa',event: 'Did Something'})

@segmentio/gateway @thesmart

Closes#75.

[f2prateek]

I can't tell, but what's the behaviour if you call analyticsMock.track({}). Does it throw an exception like the real client or silently swallow it?

[stephenmathieson]

The "real" client would throw, the mock would not. I think you're on to something here - this could cause all sorts of confusion if things worked in dev/test but threw in prod. I'll refactor tomorrow after I get some sprint work done.

[stephenmathieson]

Thinking about this a bit further, I don't think it's worth us supporting a mock. The monkey patch from #75 is only 3 SLOC - users can add it on their own.

[f2prateek]

so can we close #75 as well?