add history cache to htmax but make it opt in via config#3898
Open
MichaelWest22 wants to merge 4 commits into
Open
add history cache to htmax but make it opt in via config#3898MichaelWest22 wants to merge 4 commits into
MichaelWest22 wants to merge 4 commits into
Conversation
MichaelWest22
force-pushed
the
htmax-cache
branch
from
July 18, 2026 15:49
17ef2a4 to
6e5b269
Compare
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.
Description
htmax can include the history cache extension if we set it to default to disabled like this. We can add -htmax to the version data so that the cache extension can detect this version and disable the cache extension by default then. just need to add documentation on how to enable it via a meta tag and then users can opt in if they want
We should consider hx-ptag, hx-upsert and hx-alpine-compat as safe extensions we can easily add to htmax as well.
Corresponding issue:
Testing
Please explain how you tested this change manually, and, if applicable, what new tests you added. If
you're making a change to just the website, you can omit this section.
Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded