Errors and Gotchas

Common issues

• mixing provider-specific assumptions into shared screens
• forgetting to import the stylesheet
• handling auth inside presentation components instead of server/provider boundaries
• treating Google semantics as identical to local storage semantics
• over-customizing too early instead of using view config and commands

Easy mistakes that show up quickly

• mounting LocalDriveView without a surrounding LocalDriveViewProvider
• expecting uploads to work without a driveUploadClient
• forgetting that private local assets still require server-side URL access checks
• assuming every Google file has a direct download URL
• forgetting to clear or reconcile selection after bulk actions

Practical advice

• keep server contracts explicit
• keep URL/search state stable for list-heavy screens
• document provider differences for your team
• start with shared primitives and add product behavior one layer at a time

Heuristic

If a bug feels visual, inspect page composition and view config.

If a bug feels provider-specific, inspect the provider service and server helpers first.

If a bug feels like permissions or file opening, inspect the route handler and auth boundary before changing the UI.