[Vectorize] Replace manually set wrangler commands with WranglerNamespace component #26462
+9
−215
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kodster28
requested review from
a team,
GregBrimble,
WalshyDev,
elithrar,
irvinebroque,
mchenco,
mikenomitch,
sejoker and
vy-ton
as code owners
github-actions
bot
added
size/m
product:vectorize
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
kodster28
commented
Nov 12, 2025
Contributor
|
LGTM! |
Oxyjun
approved these changes
Nov 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This moves the Wrangler Commands associated with Vectorize to a more complete, more sustainable pattern (where we automatically pull in the information from
wrangler --helpto build out all the commands under the Vectorize namespace.This promotes better consistency, reduces work between repos, and makes sure that new flags or commands don't get forgotten.
For additional context, refer to CED-177.
Validation steps
For testing, the team should compare the arguments between the preview build and the current build to make sure things aren't getting lost in translation.
If there are updates that need to happen, you'd want to update your help text in Wrangler itself (which'll then flow back into docs once this change is live -- and once we bump our own Wrangler version).
Related
#24600
#24597