stpe / mixpanel-engage-query Goto Github PK

As per documentation the -p parameter takes input with field separated by commas, but in using it on my environment I have with trial and error figured that actually the field names should be space separated.

e.g.:

engage -p '$email,$first_name'
(does not work)

engage -p '$email $first_name'
(works fine)

Would be nice to fix in the doc so other people who run into this don't waste time.

A little suggestion :
I have a lot of properties that contain spaces into their name. I can't use them with p and r parameters because the split is done on space. If the split is done on comma, I could use property name with space.
Or, if we split on space, add the possibility to use quote for properties with spaces.

By the way, this is an excellent script ;) thank you !

You README and .env files have all mixpanel api key an secrets
degoo_MIXPANEL_API_KEY=f89785f7a01dbe7662099c6ea04b88b4
degoo_MIXPANEL_API_SECRET=a69aa385a71f8de23fdff5ed55cabb26
MIXPANEL_API_KEY=55dcba882ca5ce49e8306aae1c8399b6
MIXPANEL_API_SECRET=4f8a8f7f8a22c3357932221136132b0c

Remove them before someone misuses :)

https://codewithhugo.com/how-to-make-beautiful-simple-cli-apps-with-node/

To avoid having to re-enter it on the cmd line all the time.

When I try to run a query using the "-q" switch I get a error message that the filename or directory name is incorrect. However if I just run the command by itself without trying to query I can generate results. Is there something I'm not doing correctly here? Any help would be greatly appreciated.

Support .*rc file for keeping api credentials, i.e. ~/.engagerc

Especially useful in case of global npm installation since it is awkward to work with an .env file in the script's directory.

Getting expired request, how and where is 'expire' defined?