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

Incorrect path in debug mode #143

Closed
baiwusanyu-c opened this issue Mar 23, 2023 · 1 comment
Closed

Incorrect path in debug mode #143

baiwusanyu-c opened this issue Mar 23, 2023 · 1 comment

Comments

@baiwusanyu-c
Copy link

Describe the bug
The read path is incorrect when using the resolve function in the two modes of debugging test and running test

To Reproduce
Steps to reproduce the behavior on the example project:

  1. Run the test code in debug mode and observe the path value at the debugger
    image

  2. Run the test code directly in regular mode
    image

Expected behavior
path value match

Screenshots
debugger.....
image
regular mode....
image

Environment

(Paste info.txt content generated by the example project)

  • OS: win10
  • VSCode version:1.76.2
  • Vitest version:^0.29.2
  • Vitest plugin version:v0.2.39

Additional context
There is no problem running in webstorm, it should not be a problem with vitest itself

test('foo', () => {
   
    const foo = `${resolve()}`
    debugger
    expect(foo ).toBe('D:\\project-github\\unplugin-vue-cssvars')
  })
@baiwusanyu-c baiwusanyu-c added the p3-minor-bug An edge case that only affects very specific usage (priority) label Mar 23, 2023
@sheremet-va sheremet-va added pending triage and removed p3-minor-bug An edge case that only affects very specific usage (priority) labels Mar 15, 2024
@sheremet-va
Copy link
Member

sheremet-va commented Apr 3, 2024

Can you please retest with the latest pre-release version of the extension?

@sheremet-va sheremet-va closed this as not planned Won't fix, can't repro, duplicate, stale Apr 17, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants