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
fix(docs): abort before writing on a parse failure, unhang three descriptions
The guard's own TSDoc said to fail rather than guess, because the fallback
strips every hidden param from a page. The caller did the opposite: it
caught, recorded, and continued with an empty id set, and the non-zero exit
came after every page was already written. A developer who reran, saw red,
and missed the scrollback could commit a stripped page. Parse failures are
now detected in a dry pass before anything is emitted.
The zero-id guard also only fired when the array held a literal '{', so a
subBlocks built by a helper call was silently empty, while a subBlocks whose
literals only spread ({ ...sb, required: true }) hard-failed the build. It
now fires on the destructive case alone -- reporting an unreadable array
while leaving legitimate opaque spreads, which 23 blocks rely on, untouched.
Three descriptions referenced things the reader can no longer see: Dataverse
mandated base64 after its base64 row was removed, Vanta's mimeType described
itself as useful only on that removed path, and five Drive actions told the
reader to fetch a next page with no input left to accept the token.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/integrations/microsoft_dataverse.mdx
+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
@@ -387,7 +387,7 @@ Update an existing record in a Microsoft Dataverse table. Only send the columns
387
387
388
388
### Upload File to Microsoft Dataverse
389
389
390
-
Upload a file to a file or image column on a Dataverse record. Supports single-request upload for files up to 128 MB. The file content must be provided as a base64-encoded string.
390
+
Upload a file to a file or image column on a Dataverse record. Supports single-request upload for files up to 128 MB. Provide the file through the File input; its bytes are read from storage and sent to Dataverse directly.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/integrations/vanta.mdx
+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
@@ -331,7 +331,7 @@ Upload an evidence file to a Vanta document. Requires credentials with the vanta
331
331
|`documentId`| string | Yes | Unique ID of the document to attach the file to |
332
332
|`file`| file | No | The evidence file to upload |
333
333
|`fileName`| string | No | Optional file name override |
334
-
|`mimeType`| string | No | MIME type of the file \(e.g., application/pdf\); used when uploading base64 content, since uploaded files already carry their own type |
334
+
|`mimeType`| string | No | MIME type of the file \(e.g., application/pdf\); used only as a fallback when the uploaded file does not carry a content type of its own|
335
335
|`description`| string | No | Description of the uploaded evidence \(e.g., "Q3 access review evidence"\)|
336
336
|`effectiveAtDate`| string | No | ISO 8601 date indicating when the document is effective from |
0 commit comments