feat: analytics decay, frequency, timeline, changes, collect-post and native-posts - #23
Merged
Merged
Conversation
Re-pinned fopost-go to the merged deeper-analytics head, since the new analytics methods are not on its main yet.
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 six
fopost analyticssubcommands over the new endpoints in fopost/fopost#1030:decay,frequency,timeline,changes,collect-postandnative-posts.timelineandcollect-posttake a FoPost post id or a permalink, so a post made by hand on the network works the same way.changesprints the cursor to pass as the next--since, and--jsonmakes the whole thing scriptable.One note for review:
go.modpinsfopost-goat the head of its ownfeature/deeper-analyticsbranch (fopost/fopost-go#29), because the methods this uses are not on itsmainyet. Re-pin to the tagged version after that PR merges and fopost-go is tagged — otherwise this ships against a ref that only exists on a merged branch.Merge after fopost/fopost-go#29 and the API (fopost/fopost#1030).