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

refactor: Moving --legacy-env out of global #957

Merged
merged 1 commit into from
May 10, 2022

Conversation

JacobMGEvans
Copy link
Contributor

The --legacy-env flag was in global scope, which only certain commands
utilize the flag for functionality, and doesnt do anything for the other commands.

resolves #933

@changeset-bot
Copy link

changeset-bot bot commented May 10, 2022

🦋 Changeset detected

Latest commit: 073bdde

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
wrangler Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented May 10, 2022

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/runs/2303305842/npm-package-wrangler-957

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.developers.workers.dev/prs/957/npm-package-wrangler-957

Or you can use npx with this latest build directly:

npx https://prerelease-registry.developers.workers.dev/runs/2303305842/npm-package-wrangler-957 dev path/to/script.js

@JacobMGEvans JacobMGEvans marked this pull request as draft May 10, 2022 19:51
@JacobMGEvans JacobMGEvans force-pushed the move-legacy-env-flag branch from 2332f75 to 6b6657a Compare May 10, 2022 19:55
@JacobMGEvans JacobMGEvans marked this pull request as ready for review May 10, 2022 19:59
Copy link
Contributor

@petebacondarwin petebacondarwin left a comment

Choose a reason for hiding this comment

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

I agree with @threepointone about hiding this.
Otherwise LGTM!

The `--legacy-env` flag was in global scope, which only certain commands
utilize the flag for functionality, and doesnt do anything for the other commands.

resolves #933
@JacobMGEvans JacobMGEvans force-pushed the move-legacy-env-flag branch from 6b6657a to 073bdde Compare May 10, 2022 20:58
@petebacondarwin petebacondarwin merged commit e0a0509 into main May 10, 2022
@petebacondarwin petebacondarwin deleted the move-legacy-env-flag branch May 10, 2022 21:10
@github-actions github-actions bot mentioned this pull request May 10, 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.

Pull out --legacy-env from global flags
3 participants