Skip to content

fix: replace sourcemap's path by the corresponding absolute file path #23

New issue

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

By clicking “No 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? No Sign in to your account

Merged
merged 1 commit into from
Jun 27, 2019

Conversation

rndmerle
Copy link
Contributor

To follow-up on #17 comments.
I'm not sure it's the best way to proceed tho.

It should work on https://github.com/bahmutov/code-coverage-vue-example.

I also tried really hard to make coverage work for code (through generated render function) but in the end I think it can't work until vuejs/vue-loader#1400 is resolved so we get two distinct source-map entries for template and script parts.

@@ -1,3 +0,0 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haha, you don't like my color theme for this repo

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haha I didn't hate it, I just assumed it had been committed by mistake :p

@bahmutov
Copy link
Contributor

ok, love it, will see if this fixes it, thank you @rndmerle

@bahmutov bahmutov merged commit 7901eb8 into cypress-io:master Jun 27, 2019
@bahmutov
Copy link
Contributor

🎉 This PR is included in version 1.6.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@bahmutov
Copy link
Contributor

Yup, I think this is it - you can see the coverage info for Vue files now https://coveralls.io/github/bahmutov/code-coverage-vue-example

@rndmerle
Copy link
Contributor Author

rndmerle commented Jun 27, 2019

Nice :)
If I ever get the coverage working for <template> code I'll let you know.

@bahmutov
Copy link
Contributor

bahmutov commented Jun 27, 2019 via email

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

Successfully merging this pull request may close these issues.

2 participants