Fix duplicate warning messages in wrangler dev #10913
Draft
+72
−6
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.
Fixes #6855
This PR fixes duplicate warning messages that appear during
wrangler dev
when configuration changes or state transitions occur.Changes
ConfigController.ts: Changed all 6
logger.warn()
calls tologger.once.warn()
to ensure each distinct warning only appears once per sessionTests: Added test case that verifies warnings only appear once even with multiple config updates
Key Review Points
logger.once.warn()
method exists - This assumes the logger has a.once.warn()
method that prevents duplicate messagesLink to Devin run: https://app.devin.ai/sessions/fe4aed656c5945a7adaa0078b1e9e9a8
Requested by: [email protected]