Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[reJest] Fixes problem with opacity comparation #6233

Merged
merged 2 commits into from
Jul 16, 2024

Conversation

piaskowyk
Copy link
Member

Summary

Due to some platform limitations, certain properties may not be exact values as originally set, for example, opacity. This PR introduces new comparators, CLOSE_DISTANCE and FLOAT, which can be used in cases where we can't achieve the exact value as originally set.

@piaskowyk piaskowyk requested a review from Latropos July 8, 2024 13:23
Copy link
Contributor

@Latropos Latropos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! However I wish you renamed CLOSE_DISTANCE to CLOSE_NUMBER, it seems a bit more accurate

@piaskowyk
Copy link
Member Author

I named it CLOSE_DISTANCE to maintain naming conventions, as the DISTANCE mode already exists.

@piaskowyk piaskowyk added this pull request to the merge queue Jul 16, 2024
Merged via the queue into main with commit 7f0a083 Jul 16, 2024
5 checks passed
@piaskowyk piaskowyk deleted the @piaskowyk/close-distance branch July 16, 2024 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants