kaustav202 / kaustav202/RealTime-TwitterDataAnalysis
Doc Update [ Tweet JSON Structure ]
- Dominant language
- Python
- Stars
- 36
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
* **I'm submitting a ...**
- [ ] bug report
- [ ] feature request
- [x] change/modification
- [ ] design issue
* **Do you want to request a *feature* or report a *bug*?**
* **What is the current behavior?**
* **If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem**
* **What is the expected behavior?**
Add a clear diagram showing the structure of the JSON response / tweet statuses received from the Twitter API
* **What is the motivation / use case for changing the behavior?**
The whole project revolves around utilizing the tweets (json) for analysis and experimental processes, hence it's important to highlight the structure, hierarchy and fields of the respective data.
* **Other information** (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
Contributor guide
Assessment
This issue has not been assessed yet.