Commands

DriveViewCommands lets you define:

• node commands for a single row or card
• selectedNodes commands for bulk selection actions

Those commands are passed into createDriveViewConfig() and then exposed to the active view.

Why this is useful

You can keep product actions close to the screen that owns them, while still letting the shared Drive components decide where to render them.

In the current implementation, selected-node commands power a floating command menu in both local and Google grid views.

This is the right place to connect product actions such as:

• rename
• archive
• restore
• duplicate metadata
• publish asset
• attach file to another entity

Recommendation

Use provider command components for provider-native operations such as folder creation or file update, then add your own business commands on top instead of forking the view layer.