This repository was archived by the owner on Sep 29, 2023. It is now read-only.
REST API Docs #297
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,377 @@ | ||
| <p>Appwrite supports multiple protocols for accessing the server, including <a href="/docs/rest">REST</a>, <a href="/docs/graphql">GraphQL</a>, and <a href="/docs/realtime">Realtime</a>.</p> | ||
|
|
||
| <p>The REST API allows you to access your Appwrite server through HTTP requests, without the need for an SDK. Each endpoint in the API represents a specific operation on a specific resource.</p> | ||
|
|
||
| <h2><a href="/docs/rest#headers" id="headers">Headers</a></h2> | ||
| <p>Appwrite's REST APIs expect certain headers to be included with each request:</p> | ||
|
|
||
| <table class="full text-size-small"> | ||
| <thead> | ||
| <tr> | ||
| <td style="width: 300px">Header</td> | ||
| <td style="width: 80px"></td> | ||
| <td>Description</td> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td><code>X-Appwrite-Project: [PROJECT-ID]</code></td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td>Provides the ID of your Appwrite Project to the REST API.</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Content-Type: application/json</code></td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td>Declares content type of the HTTP request.</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>X-Appwrite-Key: [API-KEY]</code></td> | ||
stnguyen90 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| <td><span class="tag red">optional</span></td> | ||
gewenyu99 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <td>Used for authentication in server integrations. <b>Do not use API keys in client applications.</b></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>X-Appwrite-Response-Format: [VERSION-NUMBER]</code></td> | ||
| <td><span class="tag red">optional</span></td> | ||
gewenyu99 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <td>Used for backwards compatibility. The response will be formatted to be compatible the provided version number.</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>X-Fallback-Cookies: [FALLBACK-COOKIES]</code></td> | ||
| <td><span class="tag red">optional</span></td> | ||
gewenyu99 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <td>Used in scenarios where browsers do not allow third-party cookies. Often used when there is no <a href="/docs/custom-domains">Custom Domain</a>.</td> | ||
| </tr> | ||
| </tbody> | ||
gewenyu99 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| </table> | ||
|
|
||
| <h3><a href="/docs/rest#no-headers" id="no-headers">Using Appwrite Without Headers</a></h3> | ||
| <p>Some use cases do not allow the use of custom headers, such as when embedding images from Appwrite in HTML. In these cases, you can provide the Appwrite project ID using the query parameter <code>project</code>.</p> | ||
| <div class="ide margin-bottom" data-lang="html" data-lang-label="HTML"> | ||
| <pre class="line-numbers"><code class="prism language-html" data-prism><?php echo htmlentities('<img src="https://[HOSTNAME_OR_IP]/v1/storage/buckets/[BUCKET_ID]/files/[FILE_ID]/preview?project=[PROJECT_ID]">'); ?></code></pre> | ||
abnegate marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| </div> | ||
|
|
||
| <h3>Client Authentication</h3> | ||
gewenyu99 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <p>You can create account sessions with POST requests to the <a href="docs/client/account">Account API</a>. Sessions are persisted using cookies. You can learn more about session persistence in the <a href="/docs/authentication#persistence">Authentication Guide</a>.</p> | ||
| <p>The example below shows creating an account session with the <a href="/docs/client/account#accountCreateEmailSession">Create Account Session with Email</a> endpoint.</p> | ||
| <div class="ide margin-bottom" data-lang="http" data-lang-label="HTTP"> | ||
| <pre class="line-numbers"><code class="prism language-http" data-prism>POST /v1/account/sessions/email HTTP/1.1 | ||
| Host: [HOSTNAME_OR_IP] | ||
| Content-Type: application/json | ||
| X-Appwrite-Project: 5df5acd0d48c2 | ||
| X-Appwrite-Response-Format: 1.0.0 | ||
|
|
||
| {"email":"[email protected]","password":"password"}</code></pre> | ||
| </div> | ||
|
|
||
|
Member
There was a problem hiding this comment. Let's include a response to this request that shows the |
||
| <p>The cookies used to persist the session can be found in the response headers.</p> | ||
| <div class="ide margin-bottom" data-lang="http" data-lang-label="HTTP"> | ||
| <pre class="line-numbers"><code class="prism language-http" data-prism>set-cookie: a_session_61e71ec784ab035f7259_legacy=eyJpZCI6IjYzYTBkM2E1MWQ3ZGQ0NzQxOGY3Iiwic2VjcmV0IjoiYmZmN2ExZGIwYmQ3MjcyZGI5Yjg3ZmMwOGY3MzQ3MDZhYmJlYTE1ZGIzN2ViOThlZmRkMmE1OWU4NTNkODRmOGViYTAwY2E4ZjcxYzgzZTUyNDU1OTA3NDhlNTRkMDEwOTcxOTcyNTg1NWNmNDFlODg4MDg3NmI4OTk3NDJkZGFiMGQzODM1MDY0NGJlYzJkYWFiZGUyYjYyY2M1NDIwMTNjYzE0MDFhYjhiYjI2ZDdlM2E1MDgxNGVjMTc4ZDhjNTE4N2YzYzYxNWJhNTBiYWI2MjQxYTRiZjFiODA4ZDhjNGUwMTFhN2NlMzJkODRlYTI4MTU2MDVmYzkxZjg0MSJ9; expires=Tue, 19-Dec-2023 21:26:51 GMT; path=/; domain=.demo.appwrite.io; secure; httponly | ||
| set-cookie: a_session_61e71ec784ab035f7259=eyJpZCI6IjYzYTBkM2E1MWQ3ZGQ0NzQxOGY3Iiwic2VjcmV0IjoiYmZmN2ExZGIwYmQ3MjcyZGI5Yjg3ZmMwOGY3MzQ3MDZhYmJlYTE1ZGIzN2ViOThlZmRkMmE1OWU4NTNkODRmOGViYTAwY2E4ZjcxYzgzZTUyNDU1OTA3NDhlNTRkMDEwOTcxOTcyNTg1NWNmNDFlODg4MDg3NmI4OTk3NDJkZGFiMGQzODM1MDY0NGJlYzJkYWFiZGUyYjYyY2M1NDIwMTNjYzE0MDFhYjhiYjI2ZDdlM2E1MDgxNGVjMTc4ZDhjNTE4N2YzYzYxNWJhNTBiYWI2MjQxYTRiZjFiODA4ZDhjNGUwMTFhN2NlMzJkODRlYTI4MTU2MDVmYzkxZjg0MSJ9; expires=Tue, 19-Dec-2023 21:26:51 GMT; path=/; domain=.demo.appwrite.io; secure; httponly; samesite=None</code></pre> | ||
| </div> | ||
|
|
||
| <p>You will see these cookies included in subsequent requests for authentication.</p> | ||
| <div class="ide margin-bottom" data-lang="http" data-lang-label="HTTP"> | ||
| <pre class="line-numbers"><code class="prism language-http" data-prism>GET /v1/account/ HTTP/1.1 | ||
| Host: demo.appwrite.io | ||
| Cookie: a_session_61e71ec784ab035f7259_legacy=eyJpZCI6IjYzYTBkM2E1MWQ3ZGQ0NzQxOGY3Iiwic2VjcmV0IjoiYmZmN2ExZGIwYmQ3MjcyZGI5Yjg3ZmMwOGY3MzQ3MDZhYmJlYTE1ZGIzN2ViOThlZmRkMmE1OWU4NTNkODRmOGViYTAwY2E4ZjcxYzgzZTUyNDU1OTA3NDhlNTRkMDEwOTcxOTcyNTg1NWNmNDFlODg4MDg3NmI4OTk3NDJkZGFiMGQzODM1MDY0NGJlYzJkYWFiZGUyYjYyY2M1NDIwMTNjYzE0MDFhYjhiYjI2ZDdlM2E1MDgxNGVjMTc4ZDhjNTE4N2YzYzYxNWJhNTBiYWI2MjQxYTRiZjFiODA4ZDhjNGUwMTFhN2NlMzJkODRlYTI4MTU2MDVmYzkxZjg0MSJ9; a_session_61e71ec784ab035f7259=eyJpZCI6IjYzYTBkM2E1MWQ3ZGQ0NzQxOGY3Iiwic2VjcmV0IjoiYmZmN2ExZGIwYmQ3MjcyZGI5Yjg3ZmMwOGY3MzQ3MDZhYmJlYTE1ZGIzN2ViOThlZmRkMmE1OWU4NTNkODRmOGViYTAwY2E4ZjcxYzgzZTUyNDU1OTA3NDhlNTRkMDEwOTcxOTcyNTg1NWNmNDFlODg4MDg3NmI4OTk3NDJkZGFiMGQzODM1MDY0NGJlYzJkYWFiZGUyYjYyY2M1NDIwMTNjYzE0MDFhYjhiYjI2ZDdlM2E1MDgxNGVjMTc4ZDhjNTE4N2YzYzYxNWJhNTBiYWI2MjQxYTRiZjFiODA4ZDhjNGUwMTFhN2NlMzJkODRlYTI4MTU2MDVmYzkxZjg0MSJ9 | ||
| Content-Type: application/json | ||
| X-Appwrite-Project: 5df5acd0d48c2 | ||
| X-Appwrite-Response-Format: 1.0.0</code></pre> | ||
| </div> | ||
|
|
||
| <h2>Server Authentication</h2> | ||
| <p>Server integrations use API keys to authenticate and are typically used for backend applications.</p> | ||
| <p>Server APIs are authenticated with API keys instead of account sessions. Simply pass an <a href="/docs/keys">API key</a> in the <code>X-Appwrite-key: [API-KEY]</code> header with the appropriate scopes.</p> | ||
|
|
||
| <div class="ide margin-bottom" data-lang="http" data-lang-label="HTTP"> | ||
| <pre class="line-numbers"><code class="prism language-http" data-prism>GET /v1/databases/{databaseId}/collections/{collectionId}/documents HTTP/1.1 | ||
| Host: [HOSTNAME_OR_IP] | ||
| Content-Type: application/json | ||
| X-Appwrite-Project: [PROJECT_ID] | ||
| X-Appwrite-Key: [API_KEY] | ||
| X-Appwrite-Response-Format: 1.0.0</code></pre> | ||
| </div> | ||
|
|
||
| <h2>File Handling</h2> | ||
| <p>Appwrite implements resumable, chunked uploads for files larger than 5MB. Chunked uploads send files in chunks of 5MB to reduce memory footprint and increase resilience when handling large files. Appwrite SDKs will automatically handle chunked uploads but it is possible to implement this with the REST API directly.</p> | ||
|
|
||
| <p>Upload endpoints in Appwrite such as Create File and Create Deployment are different from other endpoints. These endpoints take multipart form data instead of JSON data. To implement chunked uploads, you will need to implement the following headers:</p> | ||
stnguyen90 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| <table class="full text-size-small"> | ||
| <thead> | ||
| <tr> | ||
| <td style="width: 280px">Header</td> | ||
| <td style="width: 80px"></td> | ||
| <td>Description</td> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td><code>X-Appwrite-Project: [PROJECT-ID]</code></td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td>Contains the ID of your Appwrite Project to the REST API.</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Content-Type: multipart/form-data; boundary=[FORM-BOUNDRY]</code></td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td>Contains the content type of the HTTP request and provides a <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST">boundry</a> which is used to parse the form data.</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Content-Range: bytes [BYTE-RANGE]</code></td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td>Contains information about which bytes are being transmitted in this chunk, with the format <code>[FIRST-BYTE]-[LAST-BYTE]/[TOTAL-BYTES]</code>.</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>X-Appwrite-ID: [FILE-ID]</code></td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td>Contains ID of the file this chunk belongs to.</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>X-Appwrite-Key: [API-KEY]</code></td> | ||
| <td><span class="tag red">optional</span></td> | ||
| <td>Used for authentication in server integrations. <b>Do not use API keys in client applications.</b></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| <p>The multipart form data is structured as follows:</p> | ||
|
|
||
| <table class="full text-size-small"> | ||
| <thead> | ||
| <tr> | ||
| <td style="width: 100px">Key</td> | ||
| <td style="width: 80px"></td> | ||
| <td style="width: 150px">Value</td> | ||
| <td style="width: 100px">File Name</td> | ||
| <td>Description</td> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td>fileId</td> | ||
| <td><span class="tag red">optional</span></td> | ||
| <td><code>[FILE-ID]</code></td> | ||
| <td>n/a</td> | ||
| <td>Contains the file ID of the new file. Only used by file chunks following the first chunk uploaded.</td> | ||
| </tr> | ||
| <tr> | ||
| <td>file</td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td><code>[CHUNK-DATA]</code></td> | ||
| <td><code>[FILE-NAME]</code></td> | ||
| <td>Contains file chunk data.</td> | ||
| </tr> | ||
| <tr> | ||
| <td>permissions</td> | ||
| <td><span class="tag red">required</span></td> | ||
| <td><code>[PERMISSION ARRAY]</code></td> | ||
| <td>n/a</td> | ||
| <td>Contains an array of permission strings about who can access the new file.</td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| <p>While cURL and fetch are great tools to explore other REST endpoints, it's impractical to use for chunked file uploads because you need to split files into chunks.</p> | ||
|
|
||
| <p>The multipart form data posted to file upload endpoints has the following format:</p> | ||
|
|
||
| <div class="ide margin-bottom" data-lang="http" data-lang-label="HTTP"> | ||
| <pre class="line-numbers"><code class="prism language-http" data-prism>POST /v1/storage/buckets/default/files HTTP/1.1 | ||
| Host: [HOSTNAME_OR_IP] | ||
| Content-Type: multipart/form-data; boundary=----WebKitFormBoundarye0m6iNBQNHlzTpVM | ||
| X-Appwrite-Project: demo-project | ||
| Content-Range: bytes 10485760-12582912/12582912 | ||
| X-Appwrite-ID: 6369b0bc1dcf4ff59051 | ||
|
|
||
| ------WebKitFormBoundarye0m6iNBQNHlzTpVM | ||
| Content-Disposition: form-data; name="fileId" | ||
|
|
||
| unique() | ||
| ------WebKitFormBoundarye0m6iNBQNHlzTpVM | ||
| Content-Disposition: form-data; name="file"; filename="file.txt" | ||
| Content-Type: application/octet-stream | ||
|
|
||
| [CHUNKED-DATA] | ||
| ------WebKitFormBoundarye0m6iNBQNHlzTpVM | ||
| Content-Disposition: form-data; name="permissions[]" | ||
|
|
||
| read("user:627a958ded6424a98a9f") | ||
| ------WebKitFormBoundarye0m6iNBQNHlzTpVM--</code></pre> | ||
| </div> | ||
|
|
||
| <h2>Permissions</h2> | ||
|
|
||
| <p>Appwrite SDKs have helpers to generate permission strings, but when using Appwrite without SDKs, you'd need to create the strings yourself.</p> | ||
|
|
||
| <h3>Permission Types</h3> | ||
|
|
||
| <table class="full text-size-small"> | ||
| <thead> | ||
| <tr> | ||
| <td style="width: 250px">SDK</td> | ||
| <td>Permission String</td> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td><code>Permission.read()</code></td> | ||
| <td><code>read("[PERMISSION_ROLE]")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Permission.create()</code></td> | ||
| <td><code>create("[PERMISSION_ROLE]")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Permission.update()</code></td> | ||
| <td><code>update("[PERMISSION_ROLE]")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Permission.delete()</td> | ||
| <td><code>delete("[PERMISSION_ROLE]")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Permission.write()</td> | ||
| <td><code>write("[PERMISSION_ROLE]")</code></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| <h3>Permission Roles</h3> | ||
|
|
||
| <table class="full text-size-small"> | ||
| <thead> | ||
| <tr> | ||
| <td style="width: 250px">SDK</td> | ||
| <td>Role String</td> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td><code>Role.any()</code></td> | ||
| <td><code>any</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.guests()</code></td> | ||
| <td><code>guests</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.users()</code></td> | ||
| <td><code>users</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.users([STATUS])</code></td> | ||
| <td><code>users/[STATUS]</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.user([USER_ID])</td> | ||
| <td><code>user:[USER_ID]</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.user([USER_ID], [STATUS])</td> | ||
| <td><code>user:[USER_ID]/[STATUS]</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.team([TEAM_ID])</td> | ||
| <td><code>team:[TEAM_ID]</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.team([TEAM_ID], [ROLE])</td> | ||
| <td><code>team:[TEAM_ID]/[ROLE]</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>Role.member([MEMBERSHIP_ID])</td> | ||
| <td><code>member:[MEMBERSHIP_ID]</code></td> | ||
| </tr> | ||
| </tbody> | ||
gewenyu99 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| </table> | ||
|
|
||
| <ul> | ||
| <li class="margin-bottom"><a href="/docs/permissions" rel="noopener"><i class="icon-angle-circled-right margin-start-negative-tiny margin-end-tiny"></i> Learn more about permissions</a></li> | ||
| </ul> | ||
|
|
||
| <h2>Unique ID</h2> | ||
| <p> | ||
| Appwrite's SDKs have a helper <code>ID.unqiue()</code> to generate unique IDs. When using Appwrite without an SDK, pass the string <code>"unique()"</code> into the ID parameter. | ||
| </p> | ||
|
|
||
| <h2>Query Methods</h2> | ||
gewenyu99 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <p> | ||
| Appwrite's SDKs provides a <code>Query</code> class to generate query strings. When using Appwrite without an SDK, you can template your own strings with the format below. | ||
| </p> | ||
|
|
||
| <p>Query strings are passed to Appwrite using the <code>queries</code> parameter. You can attach multiple query strings by including the array parameter multiple times in the query string: <code>queries[]="..."&queries[]="..."</code></p> | ||
|
|
||
| <table cellspacing="0" cellpadding="0" border="0" class="full margin-bottom-large"> | ||
| <thead> | ||
| <tr> | ||
| <th style="width: 150px">Query Method</th> | ||
| <th>Query String</th> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td>equal</td> | ||
| <td><code>equal("attribute", [value])</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>notEqual</td> | ||
| <td><code>notEqual("attribute", [value])</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>lessThan</td> | ||
| <td><code>lessThan("attribute", [value])</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>lessThanEqual</td> | ||
| <td><code>lessThanEqual("attribute", [value])</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>greaterThan</td> | ||
| <td><code>greaterThan("attribute", [value])</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>greaterThanEqual</td> | ||
| <td><code>greaterThanEqual("attribute", [value])</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>search</td> | ||
| <td><code>search("attribute", [value1])</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>orderDesc</td> | ||
| <td><code>orderDesc("attribute")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>orderAsc</td> | ||
| <td><code>orderAsc("attribute")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>cursorAfter</td> | ||
| <td><code>cursorAfter("documentId")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>cursorBefore</td> | ||
| <td><code>cursorBefore("documentId")</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>limit</td> | ||
| <td><code>limit(0)</code></td> | ||
| </tr> | ||
| <tr> | ||
| <td>offset</td> | ||
| <td><code>offset(0)</code></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| <div class="notice margin-bottom"> | ||
| <h3>Best Practice</h3> | ||
| <p>When using greater than, greater than or equal to, less than, or less than or equal to, it is not recommended to pass in multiple values. While the API will accept multiple values and return results with <b>or logic</b>, it's best practice to pass in only one value for performance reasons.</p> | ||
| </div> | ||
|
|
||
|
|
||
| <h2>OpenAPI and Swagger Specs</h2> | ||
| <p> | ||
| Appwrite provides a full REST API specification in the OpenAPI 3 and Swagger 2 formats every release. These can be accessed through Appwrite's GitHub repository and rendered using a variety of parsers and tools. | ||
| </p> | ||
| <ul> | ||
| <li class="margin-bottom"><a href="https://github.com/appwrite/appwrite/tree/master/app/config/specs" target="_blank" rel="noopener"><i class="icon-angle-circled-right margin-start-negative-tiny margin-end-tiny"></i> Find the REST API specification for your Appwrite version</a></li> | ||
| </ul> | ||
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.
Uh oh!
There was an error while loading. Please reload this page.