Mention Versioning Issues in Hypermedia Applications that use Fragments #130
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.
I'm opening this PR to start a discussion of versioning issues that can happen in hypermedia applications and when using htmx for fetching fragments. I feel this issue is neglected in the documentation and should be represented in a balanced way, ideally with examples on how to mitigate the issues.
Examples on when an inconsistent state could happen aways assume that the client browser loaded a full htmx page, then a server application update is deployed, and then the client executes some action that loads a fragment into the dom somewhere:
Even if these cases are rare (depends on the number of users and deployment frequency), it would be great to give devs heads-up on potential issues.