feat: read content decay, posting cadence, post timelines and native posts - #27
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the six deeper analytics endpoints from fopost/fopost#1030 to this client.
GET /v1/analytics/decayGET /v1/analytics/frequencyGET /v1/analytics/posts/:id/timelineGET /v1/analytics/changes?since=POST /v1/posts/:id/analytics/collectGET /v1/accounts/:id/native-postsA post is addressed by its FoPost id or by its permalink, URL-encoded into the path segment, so a post made by hand on the network works through the same method.
Models, a worked README section, and one test per endpoint pinning the path, the query casing and the response shape. The suite and the linters pass locally.
Merge after the API (fopost/fopost#1030), since the endpoints do not exist until it deploys.