#221 - chore(frontend): Fix Maintainability/Reliability Issues - SonarQube#344
Draft
#221 - chore(frontend): Fix Maintainability/Reliability Issues - SonarQube#344
Conversation
Collaborator
Author
|
This is a draft pull request capturing work in progress during Release 3. It is being documented here for transparency and potential future continuation. As part of the capstone handoff, we are unassigning ourselves from this 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.
Summary
This PR addresses maintainability/reliability issues identified by SonarQube in the frontend codebase. The goal is to improve code clarity and reduce technical debt without altering functionality.
Changes Made
Testing Instructions
Screenshots
Before:

Additional Notes
The
AssetsDropdown.tsx,Footer.tsx, andMapMetaData.tsxfiles still show some issues in SonarCloud. This is expected for now, as fixing these issues would change the UI, and we have decided to keep them as they are.