Allow to add file reference with drag and drop.

[v-pavanp]

It is very common use case when user wants to add reference of module file (external file) by dragging and dropping it to editor. But right now VScode is not supporting this feature. When user try to drag a file from the explorer window it is opening that file in the editor.

In the below screen shout you can compare Visual studio and VS code action for drag and drop.

[csicky]

Yes, I wanted to do just that! How I miss this feature! It was so natural in Visual Studio.

[amit-srivastava-007]

Is that feature coming in near future. Its really very tough to count nesting levels to create correct import path

[odbc789]

Is this feature ready now ?

[ganeshmuth]

When will this feature be available??

[DanJ210]

I was also hoping to get this feature in a past release as well.

[DanJ210]

Oh wow, this request was over two years ago...

[clsmt]

What's the standard way of inserting images into markdown in VSCode now? Still typing out all the commands?

[fernandogutierrez27]

is there any extension that provides this functionality??

[dskeithbuck]

Also, it would be really great if there were options for this functionality in terms of how the paths showed up.

• Explicit / Full Path
• Relative Path
• Markdown Link (uses the selected text on the line for Link Name.
  [LinkName](//path/to/file.res
• Markdown Image (uses the selected text on the line for Link Name and optionally copies to a default directory.
  [ImageName](./images/image.png)

[techsin]

+1

[csicky]

Would be a dream to have this. Maybe next year or the year after that.

Seriously, when I type the imports the stupid autocomplete tries to be smart and messes up completely, so I have to always search for a file where I used this import before, so I can copy paste it.

[Etheryte]

I think very good middle ground could be found here by making the drop event available to extensions while keeping the default behavior as-is. The drop handler in dnd.ts already has a special check for workspaces, adding a hook for extensions in a similar manner would address both use cases.

const isWorkspaceOpening = await this.doHandleDrop(untitledOrFileResources);
if (isWorkspaceOpening) {
  return;
}

const isExtensionHandled = await this.extensionService.activateByEvent('onDrop', untitledOrFileResources);
if (isExtensionHandled) {
  return;
}

Architecturally, it would make sense to have the interface exposed to extensions be very minimal, accepting a list of resources and returning a boolean value indicating whether the extension wants to interrupt the default file opening behavior.

onDrop(untitledOrFileResources: Array<IDraggedResource | IDraggedEditor>): boolean;

This would allow both pass-through and overriding behaviors for extensions while limiting the API surface that VSCode exposes.

[ericchase]

So uh... been like 5 years now. Are we still waiting for this?

[csicky]

@ericchase
This issue will never receive attention anymore. The only chance is to make a new issue, link this to that one and hope for 20 votes.

[gajrajantino]

Updates?

[ericchase]

Well, it's in the iteration plan for this month, at least.

[mjbvz]

#142990 introduces api for VS Code 1.70 that lets extensions handle dropped files (either from the VS Code explorer, editor tabs, the OS, or other applications). This extension sample shows how to use this API

This now needs to be implemented per-language by extensions. If you want to see this implemented in a given language, please file a feature request against the extension that provides support for that language

[ElecTreeFrying]

https://marketplace.visualstudio.com/items?itemName=ElecTreeFrying.drag-import-relative-path

[karlhorky]

@ElecTreeFrying amazing!! Thanks for creating this! 👏