Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path click navigate to current sources #272

Open
dzmitry-lahoda opened this issue Sep 3, 2022 · 3 comments
Open

Path click navigate to current sources #272

dzmitry-lahoda opened this issue Sep 3, 2022 · 3 comments

Comments

@dzmitry-lahoda
Copy link

dzmitry-lahoda commented Sep 3, 2022

When I build and run via nix, it see in console in case of failure of my code:

/nix/store/<hash>-foobar/my.ts
error: failed

my.ts is located in my my current local git folder in root (or it can be any other subfolder).

When I click file path it jumps to store copy.

Is it possible to make ability to jump to original file from which store one was created for editing?

Or some command to jump from store to local if stored opened first?

Will donate 5 DOT for this feature.

@hall
Copy link
Collaborator

hall commented Sep 3, 2022

Can you elaborate on "build and run via nix"? Do you mean that you have a VSCode build task? If so, can you share an example which reproduces this behavior?

@dzmitry-lahoda
Copy link
Author

image

  at async /nix/store/9imvysbavbib7l69cbscfha8cmr03xck-xcvm-demo-1.0.0/src/swap-program.ts:291:13
 nix run .#tests-up

image

So when I run via nix, I get error from nix store file, not from original as in IDE.

May be some Nix: Find source command could be to jump back to original source.

@hall
Copy link
Collaborator

hall commented Sep 9, 2022

Oh, I see, you mean the new "nix command" (too many things called the same thing 😄) which copies all files from the git index into the store before execution. So the issue isn't created by this extension but it would be nice to have an option that doesn't throw you into the store path.

I've slapped something together that should work in #275. Give it a whirl if you can and let us know whether it works for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants