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

Do not add reexported names to the exportSpecifiers list of moduleinfo #39213

Conversation

weswigham
Copy link
Member

Fixes #39195

A quick audit of the module info datapoints which were refactored into a helper function in #38809:

  • exportSpecifiers with this PR now again omits nonlocal specifiers (as all users expect only local specifiers, as they use the list to perform psuedo-name-resolution)
  • exportedBindings can contain the nonlocal exports (though didn't before Include reexported names in list of exported names #38809), since it's a map on original node ID, so including the reexports is fine (the remote entries simply won't be referenced by the users of the module info)
  • exportedNames explicitly contains the reexports now to handle live bindings (which was the intended change in Include reexported names in list of exported names #38809).

@weswigham weswigham merged commit 7893c9f into microsoft:master Jun 24, 2020
@weswigham weswigham deleted the skip-reexports-in-exportspecifiers-calculation branch June 24, 2020 01:00
cangSDARM added a commit to cangSDARM/TypeScript that referenced this pull request Jun 24, 2020
* upstream/master:
  Do not add reexported names to the exportSpecifiers list of moduleinfo (microsoft#39213)
  Update user baselines (microsoft#39214)
  Leverage syntax cursor as part of reparse (microsoft#39216)
  Update failed test tracking to support Mocha 6+ (microsoft#39211)
  Update user baselines (microsoft#39196)
  LEGO: check in for master to temporary branch.

# Conflicts:
#	src/compiler/parser.ts
Jack-Works pushed a commit to Jack-Works/TypeScript that referenced this pull request Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot set property on #<Object> which has only a getter
3 participants