-
Notifications
You must be signed in to change notification settings - Fork 32
🐛 [Frontend] Enh: Include version number in 3r party jsondiffpatch file #8195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 [Frontend] Enh: Include version number in 3r party jsondiffpatch file #8195
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the JsonDiffPatch library reference to include a specific version number (0.7.3) in the filename and manifest configuration.
- Updates the JsonDiffPatch library path to include version 0.7.3 in the filename
- Ensures consistent naming between the JavaScript wrapper and manifest configuration
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| JsonDiffPatch.js | Updates the library path to include version number 0.7.3 |
| Manifest.json | Updates the external library reference to match the versioned filename |
Comments suppressed due to low confidence (1)
services/static-webserver/client/Manifest.json:30
- The filename format is inconsistent between the two files. In JsonDiffPatch.js it's 'jsondiffpatch-0.7.3.min.js' (with hyphen) but in Manifest.json it's 'jsondiffpatch.0.7.3.min.js' (with dot). These should match for consistency.
"jsondiffpatch/jsondiffpatch.0.7.3.min.js",
|
@mergify queue |
🟠 Waiting for conditions to match
|
|



What do these changes do?
This PR simply renames the file jsondiffpatch.min.js to include its version number. In a previous PR this library was upgraded without changing its filename. This can make browsers not fetch the just upgraded library and use the one they have in the cache.
Since from some time now, users do not need to hard reload the app to get the latest version, this cached library could bring unexpected scenarios.
Related issue/s
How to test
Dev-ops