-
Notifications
You must be signed in to change notification settings - Fork 222
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
fix: use file.originalPath
instead of file.path
#218
fix: use file.originalPath
instead of file.path
#218
Conversation
I just signed the license would be great if this could be merged so we could point back to this instead of using our fork. |
I'm not sure why it's still showing as unsigned. When I click details it shows as signed |
hey this has been open for a while now. I was wondering if it could be merged? |
@tjenkinson can your add tests? |
file.originalPath
instead of file.path
@evilebottnawi how do you suggest I test this? It's a 2 line change, and there aren't any other tests. |
Hey @d3viant0ne why has this been closed it is fixing a bug isn't it? We are currently using a fork with this fix it would be nice to be able to use the main version. |
Closed the wrong PR |
Reopen it & target master |
I don't have permission to reopen |
For reference, if you click |
@tjenkinson - When you have time, rebase this with what is current master & we can get this wrapped up. |
Because other plugins (such as https://github.com/gjurgens/karma-renamer-preprocessor) may change the path.
done! |
Because other plugins (such as https://github.com/gjurgens/karma-renamer-preprocessor) may change the path.
Because other plugins (such as https://github.com/gjurgens/karma-renamer-preprocessor) may change the path.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
If this plugin is used with https://github.com/gjurgens/karma-renamer-preprocessor and
singleRun
isfalse
, it fails on subsequent builds as it is looking at the renamed path, not the original one.What is the new behavior?
If another plugin changes the path it won't effect how this works.
Does this PR introduce a breaking change?