fix: comments - add maxlength constraint in json schema

6 months ago · 148e7a71cc
2 changed files with 8 additions and 4 deletions
--- a/packages/nocodb/src/schema/swagger-v2.json
+++ b/packages/nocodb/src/schema/swagger-v2.json
@ -12897,7 +12897,8 @@
          "comment": {
            "type": "string",
            "description": "Description for the target row",
-            "example": "This is the comment for the row"
+            "example": "This is the comment for the row",
+            "maxLength": 3000
          },
          "fk_model_id": {
            "type": "string",
@ -12935,7 +12936,8 @@
          "comment": {
            "type": "string",
            "description": "Description for the target row",
-            "example": "This is the comment for the row"
+            "example": "This is the comment for the row",
+            "maxLength": 3000
          },
          "fk_model_id": {
            "type": "string",
--- a/packages/nocodb/src/schema/swagger.json
+++ b/packages/nocodb/src/schema/swagger.json
@ -18927,7 +18927,8 @@
          "comment": {
            "type": "string",
            "description": "Description for the target row",
-            "example": "This is the comment for the row"
+            "example": "This is the comment for the row",
+            "maxLength": 3000
          },
          "fk_model_id": {
            "type": "string",
@ -18965,7 +18966,8 @@
          "comment": {
            "type": "string",
            "description": "Description for the target row",
-            "example": "This is the comment for the row"
+            "example": "This is the comment for the row",
+            "maxLength": 3000
          },
          "fk_model_id": {
              "type": "string",