Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
This repository was archived by the owner on Nov 1, 2017. It is now read-only.

Commit88a3c35

Browse files
author
Chad Humphries
committed
Less than > <
1 parent9716f10 commit88a3c35

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎content/changes/2014-04-22-gist-api-now-truncating-large-files.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author_name: leongersing
77

88
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.
99

10-
###Truncating file contents> 1MB
10+
###Truncating file contentsless than 1MB
1111
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?*
1212

1313
###New files.truncated property

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp