Repository navigation
docs: expand guidance on when to use --inline - #33
Merged
Merged
Conversation
Reframe the inline section from a proxy fallback into first-class decision guidance with a size-based heuristic (inline vs static sprite vs proxy), and correct the stale note implying the proxy is the default (the static same-origin sprite is). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
Expands the
--inlinesection from "a fallback when a proxy isn't an option" into first-class decision guidance, per review discussion.What
--inline" heuristic: inline for small sprites / navigation-light apps; the default static sprite (+--hash/immutable) for large sets or high-traffic sites;--proxywhen that cached file lives on a CDN.Docs only.
🤖 Generated with Claude Code