refactor(index): freeze CACHE_HEADERS object
#377
Merged
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
There was a problem hiding this comment.
Pull Request Overview
This PR adds a JSDoc type annotation to mark the CACHE_HEADERS constant as readonly, improving type safety and code documentation.
Key Changes:
- Added
@type {Readonly<Record<string, string>>}JSDoc annotation toCACHE_HEADERSconstant
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Runtime enforcement of readonly; no doubt i'll forget otherwise
Fdawgs
changed the title
CACHE_HEADERS as readonlyCACHE_HEADERS object
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Runtime enforcement of readonly; no doubt i'll forget otherwise
Checklist
npm test