No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 0e58f0d Jun 21, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode first version Jun 13, 2018
src first version works! Jun 18, 2018
.gitattributes first version Jun 13, 2018
.gitignore first version Jun 13, 2018
.vscodeignore first version Jun 13, 2018
CHANGELOG.md first version Jun 13, 2018
LICENSE get ready Jun 21, 2018
README.md Update README.md Jun 21, 2018
package-lock.json first version Jun 13, 2018
package.json get ready Jun 21, 2018
tsconfig.json first version Jun 13, 2018
tslint.json first version Jun 13, 2018
vsc-extension-quickstart.md first version Jun 13, 2018

README.md

vscode-go-to-file

A plugin that aims to replicate some of Vim's "go to file" (gf) functionality.

A huge amount of credit goes to fr43nk/seito-openfile, whose plugin I used for the base of my work. I preferred to build my version as a standalone plugin in order to give me a plugin to work with as I learn more of the VSCode extension API.

Install from the VSCode market place: https://marketplace.visualstudio.com/items?itemName=jackfranklin.vscode-go-to-file

Features

When your cursor is hovering over a file path, invoke this plugin to be taken to that file. For example, given this code:

import foo from "./foo";

If your cursor is over the './foo' string, you will be taken to the file.

When an extension is missing, the plugin will attempt to try .js, .jsx, .scss and .css by default.

This plugin will also attempt to parse a jsconfig.json if it exists in order to find the file, so it should be able to parse aliases. For example, with these paths in jsconfig.json:

"paths": {
  "frontend/*": ["./frontend/*"],
  "testing/*": ["./src/testing/*"]
},

And an import of:

import foo from "frontend/foo";

Invoking this plugin will take you to frontend/foo.js correctly. If not, please raise an issue!

Requirements

By default this package does not bind to a key command. You should bind your own key to the command vscodeGoToFile.goToFile.

Release Notes

0.0.1

Initial release.