Skip to content

Set correct pos for NamespaceExport - #36794

Merged
Andrew Branch (andrewbranch) merged 2 commits into
microsoft:masterfrom
andrewbranch:bug/36762
Feb 14, 2020
Merged

Set correct pos for NamespaceExport#36794
Andrew Branch (andrewbranch) merged 2 commits into
microsoft:masterfrom
andrewbranch:bug/36762

Conversation

@andrewbranch

Copy link
Copy Markdown
Member

Fixes #36762

Baseline changes verify this works, but the output of a simple script is easier to look at:

ExportDeclaration (0, 27) 'export * as ns from "test";'
  NamespaceExport (6, 14) ' * as ns'
    Identifier (11, 14) ' ns'
  StringLiteral (19, 26) ' "test"'
EndOfFileToken (27, 27) ''

@Kingwl Wenlu Wang (Kingwl) left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

My fault, thanks

@andrewbranch
Andrew Branch (andrewbranch) merged commit b1e706d into microsoft:master Feb 14, 2020
Andrew Branch (andrewbranch) added a commit to andrewbranch/TypeScript that referenced this pull request Feb 14, 2020
* Set correct pos for NamespaceExport

* Update tests
Daniel Rosenwasser (DanielRosenwasser) pushed a commit that referenced this pull request Feb 14, 2020
* Fix renaming an ExportSpecifier name when propertyName is present (#36790)

* Fix renaming exportSpecifier name when propertyName is present

* Add baseline test for name without propertyName too

* Set correct pos for NamespaceExport (#36794)

* Set correct pos for NamespaceExport

* Update tests
Andrew Branch (andrewbranch) added a commit that referenced this pull request Feb 28, 2020
* Fix renaming an ExportSpecifier name when propertyName is present (#36790)

* Fix renaming exportSpecifier name when propertyName is present

* Add baseline test for name without propertyName too

* Set correct pos for NamespaceExport (#36794)

* Set correct pos for NamespaceExport

* Update tests

* Cherry-pick PR #37064 into release-3.8
@microsoft Microsoft (microsoft) locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NamespaceExport node has inconsistent width

6 participants