-
-
Notifications
You must be signed in to change notification settings - Fork 250
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
Source maps generation #1777
Open
MohammadYounes
wants to merge
8
commits into
madskristensen:master
Choose a base branch
from
MohammadYounes:f7
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Source maps generation #1777
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
fe7778c
Respect Scss.GenerateSourceMaps flag
MohammadYounes 41fe0f7
Set postcss inline map flag to false
MohammadYounes 85574ff
Respect Css.GenerateRtlSourceMaps flag and set postcss inline flag to…
MohammadYounes e03b961
Merge pull request #1835 from JoeRall/global-markdown-css-setting
madskristensen ad1d77b
Respect Scss.GenerateSourceMaps flag
MohammadYounes ce5cd64
Set postcss inline map flag to false
MohammadYounes f52358d
Respect Css.GenerateRtlSourceMaps flag and set postcss inline flag to…
MohammadYounes a4a8598
Rebase
MohammadYounes File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note:
omitSourceMapUrl
option in node-sass does not indicate the presence of source-map, but only the URL.I didn't think of autoprefixer use case before, where it would not be able to update the map file accordingly (since
sourceMappingURL
acts as a bridge). For that matter, we would need to inject thesourceMappingURL
here to CSS:Then later on:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@am11 This has nothing to do with autoprefixer being able to update the existing map. I used the flag because it indicates if source map generation is requested or not (
omitSourceMapUrl
equalsparams.sourceMapURL === undefined
).If source maps generation is always enabled, then why its conditional in both autoprefixer and rtlcss ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrong. Please re-read my previous comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm referring to input/output params, not node-sass!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
???
I totally lost you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be more clear if I had wrote it like this :
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like I said earlier, the compiler services (which support sourcemap, exception being LiveScript), should return source map to Web Essentials in all cases. WE then uses source-maps for editor extensibility features.
If sourcemap in autoprefixer is conditional, then that is a (separate) bug.
If sourcemap in RTLCss is conditional, then that is by design (because rtlcss result are returned separately).
Therefore, the real issue here is that the post-processed source-maps should overwrite those generated by node-based compiler, but it should respect the user-intended
params.sourceMapURL
option. And hence, the solution I described above would fix it. If you are still unconvinced, you can checkout the changes in srv-scss, as this is slightly out of scope for this PR. I will take care of it once the WE solution starts building again.