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

fixes invalid line offsets in merged sourcemaps #4790

Merged
merged 1 commit into from Jan 15, 2017

Conversation

peterm0x
Copy link
Contributor

Q A
Bug fix? yes
Breaking change? no
New feature? no
Deprecations? no
Spec compliancy? yes
Tests added/pass? yes
Fixed tickets possibly #4788 and others
License MIT
Doc PR

Sourcemaps generated from multiple input files have invalid line offsets.

Problem is obvious when one considers

> "one line here\n".split("\n").length
< 2

Original tests were comparing results against invalid sourcemaps, which can be readily demonstrated by inspecting them for example by source-map-visualization. Also fixed.

@codecov-io
Copy link

codecov-io commented Oct 28, 2016

Current coverage is 89.32% (diff: 100%)

No coverage report found for master at e1ac315.

Powered by Codecov. Last update e1ac315...fad6483

@hzoo
Copy link
Member

hzoo commented Nov 15, 2016

If someone can review

Didn't know about https://sokra.github.io/source-map-visualization/#custom

screen shot 2016-11-15 at 12 13 37 pm

check line 10/11

@hzoo hzoo added the PR: Bug Fix 🐛 A type of pull request used for our changelog categories label Nov 15, 2016
@kangax
Copy link
Member

kangax commented Nov 15, 2016

@hzoo did you test it by uploading a file to this service?

@hzoo
Copy link
Member

hzoo commented Nov 15, 2016

I pasted the test output but I didn't check the op

Sourcemaps generated from multiple input files have invalid line offsets.

@loganfsmyth loganfsmyth merged commit a98c9ae into babel:master Jan 15, 2017
@hzoo
Copy link
Member

hzoo commented Jan 20, 2017

@lock lock bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Oct 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated A closed issue/PR that is archived due to age. Recommended to make a new issue PR: Bug Fix 🐛 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants