Firefly-2100: Fix ESLint identified bug - #2024
Draft
aventura121 wants to merge 7 commits into
Draft
aventura121 wants to merge 7 commits into
aventura121 wants to merge 7 commits into
Conversation
…ead of string for arcsec unit
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.
Firefly-2100: "Triage (or Fix) ESLint-Identified Javascript/React Issues"
Description
This fixes ESLint identified errors with potential behavioral impacts.
I will make a separate ticket for the first one included the Jira ticket related to the use of an async function in a new Promise(). Long story short, while we could make that refactor, it doesn't change the overall behavior; and, it begs the question of what we want to do with the rejection that would be reachable.
Build
https://firefly-2100-eslint-identified-bugs-clean.irsakubedev.ipac.caltech.edu/firefly
Testing
These are syntactic errors or coding oversights that are verifiable via static analysis. I've also added unit tests where appropriate, and included manual steps for the React hook change.
Unit Testing: where appropriate, I've added unit tests to validate the changes.
Manual Testing: to validate the CombinedPinnedCharts change, we can load it into the DOM and see it renders:
Screenshot