-
Notifications
You must be signed in to change notification settings - Fork 758
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
fix: name
shouldn't be defined in environments if legacy_env = false
#623
Comments
petebacondarwin
added a commit
to petebacondarwin/wrangler2
that referenced
this issue
Mar 18, 2022
…er name Given that service environments all live off the same worker, it doesn't make sense for them to have different names. This change adds validation to tell the developer to remove such `name` fields in service environment config. Fixes cloudflare#623
petebacondarwin
added a commit
to petebacondarwin/wrangler2
that referenced
this issue
Mar 18, 2022
…er name Given that service environments all live off the same worker, it doesn't make sense for them to have different names. This change adds validation to tell the developer to remove such `name` fields in service environment config. Fixes cloudflare#623
petebacondarwin
added a commit
to petebacondarwin/wrangler2
that referenced
this issue
Mar 19, 2022
…er name Given that service environments all live off the same worker, it doesn't make sense for them to have different names. This change adds validation to tell the developer to remove such `name` fields in service environment config. Fixes cloudflare#623
petebacondarwin
added a commit
to petebacondarwin/wrangler2
that referenced
this issue
Mar 19, 2022
…er name Given that service environments all live off the same worker, it doesn't make sense for them to have different names. This change adds validation to tell the developer to remove such `name` fields in service environment config. Fixes cloudflare#623
petebacondarwin
added a commit
that referenced
this issue
Mar 20, 2022
…er name Given that service environments all live off the same worker, it doesn't make sense for them to have different names. This change adds validation to tell the developer to remove such `name` fields in service environment config. Fixes #623
Repository owner
moved this from In Review
to Done
in workers-sdk
Mar 20, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the new experimental service environments (not released yet, don't use), we shouldn't override the name of the script inside environments, since they have to all be grouped as one on the dashboard. So it should probably be an error.
The text was updated successfully, but these errors were encountered: