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

jest-haste-map/src/lib/fast_path.js relative() return wrong path #7323

Closed
yamatatsu opened this issue Nov 2, 2018 · 1 comment · Fixed by #7324
Closed

jest-haste-map/src/lib/fast_path.js relative() return wrong path #7323

yamatatsu opened this issue Nov 2, 2018 · 1 comment · Fixed by #7324

Comments

@yamatatsu
Copy link
Contributor

🐛 Bug Report

fast_path#relative() in jest-haste-map return sliced dir name, when filename start with words same rootDir.

ex)
dirname: foo/bar
filename: foo/barbaz/index.js

And relative() return az/index.js

To Reproduce

Steps to reproduce the behavior:

Expected behavior

When:
dirname: foo/bar
filename: foo/barbaz/index.js

And should get ../barbaz/index.js

Link to repl or repo (highly encouraged)

Please provide either a repl.it demo or a minimal repository on GitHub.

Issues without a reproduction link are likely to stall.

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: macOS High Sierra 10.13.6
    CPU: x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
  Binaries:
    Node: 8.11.3 - ~/.config/fnm/bin/node
    Yarn: 1.10.1 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant