More explicit explanation of htmx.config.getCacheBusterParam #2376
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.
Description
The documentation for
htmx.config.getCacheBusterParam
can be confusing. Colleagues and I expected an ephemeral timestamp or random number, not the target element id. I have tried to clarify its behaviour in the docs:Original text is "defaults to false, if set to true htmx will include a cache-busting parameter in GET requests to avoid caching partial responses by the browser"
New text is "defaults to false, if set to true htmx will append the target element to the GET request in the format
org.htmx.cache-buster=targetElementId
"For reference the behaviour is implemented here
htmx/src/htmx.js
Line 3204 in ba2c30b
Note the tests are well phrased in this regard
htmx/test/attributes/hx-get.js
Line 113 in ba2c30b