Optionally save data in json format
Closed this issue · 2 comments
dhudsmith commented
This would be convenient if you're pulling data that contains a nested data structure (for example, if pulling the entities expansion for tweets). I'm thinking just add an option in the yaml file that allows you to save the tweet or user data as json.
NickDeas commented
Partially addressed in Pull Request #22. With these commits, the optional save as json still flattens the data in multiple table as the csv format does.
dhudsmith commented
That's good enough for me.