Remove unused response.clone in service worker fetch handler #312
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
👷 Deploy request for weather-available pending review.Visit the deploys page to approve it
|
|
Owner
|
Good work @GK-302 |
GauravKarakoti
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Title :Remove unused response.clone in service worker fetch handler
Closes #293
📌 Description
Removes an unnecessary response.clone() in the service worker’s fetch event handler (sw.js). The first clone was never used, which caused minor inefficiency and reduced code clarity.
Details:
Only the clone used for caching is kept.
No functional changes; performance and readability improvement.