-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
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
Support for collecting spond posts #96
base: main
Are you sure you want to change the base?
Conversation
Fixed wrong explanation for the use of `{date }`
UID of the group. | ||
prevuid : str | ||
Different UID used on the webpage, optional to use when calling this function. | ||
date : str |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be an optional datetime, like in get_events()
, not a string.
uid : str | ||
UID of the group. | ||
prevuid : str | ||
Different UID used on the webpage, optional to use when calling this function. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would someone actually use prevuid
- can you give an example? If it's optional, it should be coded as such.
Yes, I think this is necessary. 1000 seems a lot - is there an inbuilt default when calling the API without this parameter? |
Added API call
get_posts()
for reading last 1K posts.Amount of collected posts could be set to use input value in the function instead of defaulting to 1K:
max=SOME_VARIABLE
.