Expose last X headers for extensability #353
Merged
+16
−2
Conversation
This file contains 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
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.
I'm developing an add-on plugin for the Autopost for X plugin that shows X API usage statistics in the WordPress admin for a client. Since there's no dedicated endpoint to retrieve these stats, I'll rely on the headers returned by the API when a tweet is posted. By hooking into the
autoshare_for_twitter_after_status_updateaction, I can access these headers and extract key information, such as the current rate limit and reset time.How to test the Change
Changelog Entry
Credits
Props @s3rgiosan
Checklist: