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

Avoid name conflicts when inlining dynamic imports nested in functions #3256

Merged
merged 3 commits into from Nov 25, 2019

Conversation

lukastaegert
Copy link
Member

This PR contains:

  • bugfix
  • feature
  • refactor
  • documentation
  • other

Are tests included?

  • yes (bugfixes and features will not be merged without tests)
  • no

Breaking Changes?

  • yes (breaking changes will not be merged unless absolutely necessary)
  • no

List any relevant issue numbers:
resolves #3245

Description

This makes sure that when a dynamic import is used inside a function, variables inside this function are deconflicted with respect to the inlined namespace.

@codecov
Copy link

codecov bot commented Nov 25, 2019

Codecov Report

Merging #3256 into master will increase coverage by 0.04%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #3256      +/-   ##
==========================================
+ Coverage   92.74%   92.79%   +0.04%     
==========================================
  Files         170      170              
  Lines        5925     5923       -2     
  Branches     1793     1792       -1     
==========================================
+ Hits         5495     5496       +1     
+ Misses        224      223       -1     
+ Partials      206      204       -2
Impacted Files Coverage Δ
src/ast/nodes/ImportExpression.ts 100% <100%> (ø) ⬆️
src/utils/deconflictChunk.ts 100% <100%> (ø) ⬆️
src/ast/scopes/ChildScope.ts 100% <100%> (+4.65%) ⬆️
src/ast/nodes/shared/Node.ts 91.42% <0%> (+1.42%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 99a715a...b9ea0e4. Read the comment docs.

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

Successfully merging this pull request may close these issues.

Variable name conflicts when using inlineDynamicImports
1 participant