Tulip Logo IconTulip
Reference

Types

Important public types live around contracts, validators, view state, and provider-specific node schemas.

Shared areas to know

  • Drive, DriveReader, and optional capability contracts
  • DTO and validator types for folders, uploads, and list filters
  • DriveViewMode
  • DriveViewCommands
  • DriveSelectionContextValue

Local-provider types worth knowing

  • LocalDriveNode
  • LocalDriveFileNode
  • LocalDriveNodeWithAsset
  • PresignLocalDriveFileInput
  • UpdateLocalDriveNodeInput
  • LocalDriveUploadClient

Google-provider types worth knowing

  • GoogleDriveNode
  • GoogleDriveNodeWithChildren
  • UpdateGoogleDriveNodeInput
  • GoogleDriveTableFilters

Guidance

Prefer consuming public exported types from package entrypoints instead of reaching into internal paths from application code.

Also prefer depending on shared contracts when possible. Only use provider-specific node types when your screen truly needs provider-specific metadata such as assetId or webViewLink.

Exports

The Drive package is split into shared, local, and Google entrypoints.

Errors and Gotchas

Common integration mistakes and design pitfalls when wiring Drive into a real product.

On this page

Shared areas to knowLocal-provider types worth knowingGoogle-provider types worth knowingGuidance