Merge pull request #50 from seatable/5.3-changes

Changes for SeaTable 5.3

Author: christophdb

.github/workflows/rdme-openapi.yml

@@ -74,12 +74,6 @@ jobs:
         with:
           rdme: openapi base_operations.yaml --key=${{ secrets.README_API_KEY }} --id=67812a09e88eab0a89818909 --useSpecVersion
 
-      # base operations (before 4.4)
-      - name: Update base operations 🚀
-        uses: readmeio/rdme@v8
-        with:
-          rdme: openapi base_operations_deprecated.yaml --key=${{ secrets.README_API_KEY }} --id=67812a09e88eab0a89818902 --useSpecVersion
-
       # file operations
       - name: Update file operations 🚀
         uses: readmeio/rdme@v8

intro/changelog.md

@@ -18,7 +18,7 @@ Listed below are all the changes to the SeaTable API. Each date corresponds to a
 
 > ❗ Important Update: API Endpoint Changes
 >
-> In version 5.2, the `/dtable-server` and `/dtable-db` endpoints will be deprecated and then removed in version 6.0. All functions will be transitioned to `/api-gateway` endpoints. Please update your custom integrations and scripts accordingly to ensure continued functionality. More information will be provided with the release notes of SeaTable version 5.2.
+> In version 5.2, the `/dtable-server` and `/dtable-db` endpoints will be deprecated and then removed in version 5.3. All functions will be transitioned to `/api-gateway` endpoints. Please update your custom integrations and scripts accordingly to ensure continued functionality. More information will be provided with the release notes of SeaTable version 5.2.
 
 > 📘 New requests
 >

intro/introduction.md

@@ -111,14 +111,14 @@ Note down the name of the tables and the name of the columns. You will need thes
 
 ### Step 4: Write some data to your base
 
-The request to [Add a row](https://api.seatable.com/reference/addrowdeprecated) to a base, requires the following information. You have to know ...
+The request to [Append Rows](https://api.seatable.io/reference/appendrows) to a base, requires the following information. You have to know ...
 
 - the `Base-Token` for authentication -> ok
 - the `base_uuid` to identify the base -> no problem
 - the `table_name` -> you should know this from the last request
-- and you have to define the row object, meaning that you have to tell the API what values you want to write to the table.
+- and you have to define the row object(s), meaning that you have to tell the API what values you want to write to the table.
 
-At first it looks difficult to define the row object, but in fact it is quite easy. The row object consists of key:value pairs. The key is the name of the column and the value is that what you want to write to the base. So if you want to create a line with **John Doe**, then the row object looks like this:
+At first it looks difficult to define the row objects, but in fact it is quite easy. The row objects consist of key:value pairs. The key is the name of the column and the value is that what you want to write to the base. So if you want to create a row with **John Doe**, then the row object looks like this:
 
 ```json Row object, writing some values to the columns with the name First name and Last name.
 {

intro/limits.md

@@ -26,7 +26,7 @@ Meaning that if you reach the rate limit for one base, you still could make requ
 
 > ❗ Important Update: API Endpoint Changes
 >
-> In version 5.2, the `/dtable-server` and `/dtable-db` endpoints will be deprecated and then removed in version 6.0. All functions will be transitioned to `/api-gateway` endpoints. Please update your custom integrations and scripts accordingly to ensure continued functionality. More information will be provided with the release notes of SeaTable version 5.2.
+> In version 5.2, the `/dtable-server` and `/dtable-db` endpoints will be deprecated and then removed in version 5.3. All functions will be transitioned to `/api-gateway` endpoints. Please update your custom integrations and scripts accordingly to ensure continued functionality. More information will be provided with the release notes of SeaTable version 5.2.
 
 ### Retrieve current rate limit usage
 

intro/models.md

@@ -190,9 +190,7 @@ SeaTable offers some column types that are **filled automatically**. It is not p
 
 ### Handling of default values
 
-If you use the old [Append Rows](https://api.seatable.com/reference/appendrowsdeprecated) endpoint, the **default values** of the text, number and single select column types **won't be filled** by the API request automatically. If you leave these fields blank, they'll also be blank after the new row is appended, which is different than the behavior on the web UI.
-
-If you use the new [Append Rows](https://api.seatable.com/reference/appendrows) endpoint, you can set the `apply_default` body parameter to `true`, which ensures that any default values are automatically applied.
+If you use the [Append Rows](https://api.seatable.io/reference/appendrows) endpoint, you can set the `apply_default` body parameter to `true`, which ensures that any default values are automatically applied.
 
 ---
 

tests/__snapshots__/test_base_operations/test_appendRows[appendRowsDeprecated].json

@@ -26,7 +26,6 @@
       "groups": [],
       "hidden_columns": [],
       "is_locked": false,
-      "link_rows": {},
       "name": "Default View",
       "private_for": null,
       "row_height": "default",