Skip to content

Conversation

@pluethi1
Copy link
Contributor

@pluethi1 pluethi1 commented Oct 15, 2021

Changes are basically the same as the PR addressing the same issue in the JS project jquery/esprima#2055

fixes #195

public readonly Identifier? Exported;

public ExportAllDeclaration(Literal source) : base(Nodes.ExportAllDeclaration)
public ExportAllDeclaration(Literal source, Identifier? exported) : base(Nodes.ExportAllDeclaration)
Copy link
Owner

Choose a reason for hiding this comment

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

@lahma would it be better to create another ctor so it's not a breaking change?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Good catch, as type is public and we don't have JS semantics where nothing matters having another constructor makes sense in minor release.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Hard to say if there's any dependency, but follows semantic versioning.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@lahma would it be better to create another ctor so it's not a breaking change?

I added another commit to this PR that adds another constructor

@lahma
Copy link
Collaborator

lahma commented Oct 15, 2021

Great work @pluethi1 ! Could you check the constructor comment? Looks like ready for the prime time otherwise.

@lahma lahma merged commit b25a870 into sebastienros:main Oct 18, 2021
@adams85 adams85 mentioned this pull request Apr 24, 2022
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.

Support for exporting another module's contents as namespace

3 participants