feat: add frontend version checking for outdated clients #2727
Conversation
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
Introduce `FrontendVersion` middleware to backend to attach the current frontend version hash in the HTTP response headers. This allows the client to detect if the frontend version is outdated. Create a new `FrontendOutdatedDialog` Vue component that watches for changes in the frontend version and prompts users to reload if they are running an outdated version. Integrate this component into the main application layout. Update the `Api` service to set up an Axios interceptor to read the 'X-Frontend-Version' header from responses and store it in the settings store, triggering the version check logic. Enhance user experience by ensuring they always use the latest client features and bug fixes.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2727 +/- ##
=============================================
- Coverage 96.74% 96.71% -0.04%
- Complexity 1823 1825 +2
=============================================
Files 439 441 +2
Lines 12478 12509 +31
Branches 2080 2083 +3
=============================================
+ Hits 12072 12098 +26
- Misses 406 411 +5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
PILOS
|
||||||||||||||||||||||||||||
| Project |
PILOS
|
| Branch Review |
handle-frontend-outdated
|
| Run status |
|
| Run duration | 07m 47s |
| Commit |
|
| Committer | Samuel Weirich |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
0
|
Skipped
|
0
|
Passing
|
610
|
| View all changes introduced in this branch ↗︎ | |
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.
Introduce
FrontendVersionmiddleware to backend to attach the current frontend version hash in the HTTP response headers. This allows the client to detect if the frontend version is outdated.Create a new
FrontendOutdatedDialogVue component that watches for changes in the frontend version and prompts users to reload if they are running an outdated version. Integrate this component into the main application layout.Update the
Apiservice to set up an Axios interceptor to read the 'X-Frontend-Version' header from responses and store it in the settings store, triggering the version check logic.Enhance user experience by ensuring they always use the latest client features and bug fixes.
Fixes #
Type
Checklist
Changes
Other information