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

Removing x namespace from go/python/nodejs automation packages #6518

Merged
merged 3 commits into from Mar 17, 2021

Conversation

stack72
Copy link
Contributor

@stack72 stack72 commented Mar 12, 2021

All of these were moved with git mv so that we preserve the history!

@stack72 stack72 requested a review from komalali March 12, 2021 17:27
@stack72 stack72 self-assigned this Mar 12, 2021
@stack72 stack72 changed the title Moving sdk/go/x/auto to sdk/go/auto Removing x namespace from go/python/nodejs automation packages Mar 12, 2021
@stack72 stack72 force-pushed the move-go-automation-api branch 2 times, most recently from 6d3b74a to d3a7a79 Compare March 12, 2021 19:40
Copy link
Member

@komalali komalali left a comment

Choose a reason for hiding this comment

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

This looks 99% of the way there. I think we're just missing exporting automation from the top-level index.ts for nodejs.

@stack72
Copy link
Contributor Author

stack72 commented Mar 16, 2021

This looks 99% of the way there. I think we're just missing exporting automation from the top-level index.ts for nodejs.

Interesting - the original module didn't have the import of X so I didn't remove anything there - if this was needed wouldn't the tests fail?

@komalali
Copy link
Member

komalali commented Mar 16, 2021

It's not "needed" like it would make the tests fail (since the tests are using relative imports), but it is needed so folks can do import {automation} from "@pulumi/pulumi" - it was probably an oversight that this was left out initially. If you look at the top-level index.ts it includes all of the other submodules.

Right now the only way to import from the automation module is to do something like import { InlineProgramArgs, LocalWorkspace } from "@pulumi/pulumi/automation"; which is inconsistent with the rest of our modules.

@stack72
Copy link
Contributor Author

stack72 commented Mar 16, 2021

It's not "needed" like it would make the tests fail (since the tests are using relative imports), but it is needed so folks can do import {automation} from "@pulumi/pulumi" - it was probably an oversight that this was left out initially. If you look at the top-level index.ts it includes all of the other submodules.

Right now the only way to import from the automation module is to do something like import { InlineProgramArgs, LocalWorkspace } from "@pulumi/pulumi/automation"; which is inconsistent with the rest of our modules.

gotcha!! Then it's a good thing to add :)

Copy link
Member

@komalali komalali left a comment

Choose a reason for hiding this comment

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

:shipit:

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.

None yet

2 participants