Drive integration opens diagrams in Draw (link file, no renderer needed)

[vibhavkatre]

What

register_in_drive now registers a Draw diagram in Frappe Drive as a link File whose target is the Draw editor route (/draw/d/<name>), via drive.api.files.create_link.

So a diagram shows up in the user's Drive and clicking it opens the diagram in Draw — closing the last launch gap (#4) with no Drive-side renderer/repo change required.

Why this approach

The previous native-doc linkage (content_doctype=Draw Diagram) would have needed a Drive-side viewer for the content type — a change in the Drive repo, out of scope for this app. A link file needs nothing on the Drive side and still lands the diagram in Drive with a working open action.

Changes

• api/drive_integration.py: diagram_link(name) → /draw/d/<name>; register_in_drive creates the Drive link in the user's team, idempotent by file_url, still a clean no-op when Drive is absent / has no team.
• test_draw_diagram.py: asserts the registered File is a link to /draw/d/<name> + idempotency.

Testing

Verified locally with Drive installed: run-tests --app draw → 9 pass (creates a team, registers the link, confirms file_url + idempotency). CI (fresh site, no Drive) skips the Drive-present case, as before.

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 4/5

Safe to merge; the only gap is a stale module-level comment describing the old approach.

The logic change is small and well-tested. The module docstring at the top of drive_integration.py still describes the discarded content_doctype approach, which will mislead future readers, but does not affect runtime behaviour.

draw/api/drive_integration.py — the header comment (lines 6–10) needs to be updated to reflect the link-file approach.

_{Reviews (1): Last reviewed commit: "Frappe Draw: Drive integration opens dia..." | Re-trigger Greptile}