fix(footer): handle null/undefined version data gracefully#385
Open
Ishitadubeyy wants to merge 1 commit into
Open
fix(footer): handle null/undefined version data gracefully#385Ishitadubeyy wants to merge 1 commit into
Ishitadubeyy wants to merge 1 commit into
Conversation
Prevent footer from displaying null or undefined values when version data is unavailable.
|
This pull request has conflicts, please rebase to resolve those before we can evaluate the pull request. |
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.
This PR improves the footer by handling missing or unavailable version metadata more gracefully.
Previously, when the backend version information was not available or not configured, the footer could display null or undefined values directly in the UI. This created a poor user experience, especially for contributors or users running the frontend without a fully configured backend environment.
This change ensures that the footer now shows a clean fallback message instead of rendering incomplete metadata.
Changes
Updated the footer rendering logic to safely handle missing version information
Prevented null and undefined values from appearing in the UI
Added a fallback message when version metadata is unavailable
How to test
Run the application without backend version information available
Open the UI and check the footer section
Confirm that it no longer displays null or undefined
Verify that a clean fallback message such as "Version information unavailable" is shown instead
If backend version data is available, confirm that the footer still renders version details correctly
Closes #243