You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 1, 2017. It is now read-only.
Copy file name to clipboardExpand all lines: content/changes/2014-04-22-gist-api-now-truncating-large-files.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author_name: leongersing
7
7
8
8
In order to provide the most robust, fast and accurate API for Gist we recently decided to make a few small changes to the*files* payload.
9
9
10
-
###Truncating file contents> 1MB
10
+
###Truncating file contentsless than 1MB
11
11
Sometimes we need to put some large data into a gist. However, we don't always need to see the full content of that large gist when we're fetching the metadata for gists via the API. This change imposes a sensible (according to our data) limit on the amount of raw file data that is returned in gist fetches via the API. If you're relying on reading the full content of individual files from a gist then you may need to update your flow to perform a followup request for the```raw_url``` resource in order to download the entire contents of the file. Which begs the question:*How do I know if the file's contents have been truncated?*