Repository navigation
Replace parseFloat with Number.parseFloat in E2E tests - #682
Merged
Merged
Conversation
Co-authored-by: manusa <488391+manusa@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix prefer number.parseFloat over parseFloat in tests
Replace parseFloat with Number.parseFloat in E2E tests
Nov 5, 2025
manusa
marked this pull request as ready for review
November 6, 2025 05:45
manusa
approved these changes
Nov 6, 2025
|
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.



Sonar flagged usage of global
parseFloatinstead ofNumber.parseFloatat lines 311 and 338 insrc/__tests__/task-manager.test.e2e.js.Changes
parseFloat(opacity)withNumber.parseFloat(opacity)in two test assertionsOriginal prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.