We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I was reading the code https://github.com/tweepy/tweepy/blob/master/tweepy/models.py#L315 one question came to my mind about the way the models where designed.
Would not it be better do use dataclasses in here with some default values? When working with the Status model it is not obvious what are the properties of Status object without checking the twitter documentation: https://developer.twitter.com/en/docs/twitter-api/v1/data-dictionary/object-model/tweet
dataclasses
properties
Status
It would be good to give some hints to the user about what fields he can expect in a model.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When I was reading the code https://github.com/tweepy/tweepy/blob/master/tweepy/models.py#L315 one question came to my mind about the way the models where designed.
Would not it be better do use
dataclassesin here with some default values? When working with the Status model it is not obvious what are thepropertiesofStatusobject without checking the twitter documentation: https://developer.twitter.com/en/docs/twitter-api/v1/data-dictionary/object-model/tweetIt would be good to give some hints to the user about what fields he can expect in a model.
The text was updated successfully, but these errors were encountered: