Skip to content

Fix float double equality checks in DTO comparers - #433

Merged
zeynepatsoprasteria merged 3 commits into
developmentfrom
426-generated-dto-comparers-treat-equal-floating-point-values-as-different-nearlyequal-not-negated
Nov 10, 2026
Merged

zeynepatsoprasteria merged 3 commits into
developmentfrom
426-generated-dto-comparers-treat-equal-floating-point-values-as-different-nearlyequal-not-negated

Conversation

@zeynepatsoprasteria

Copy link
Copy Markdown
Contributor

Prerequisites

  • I have written a descriptive pull-request title
  • I have verified that there are no overlapping pull-requests open
  • I have verified that I am following the SysML2.NET code style guidelines
  • I have provided test coverage for my change (where applicable)

Description

Fix #426 issue for the DTO float double comparison check. The Sonarqube check was also applied. But, the refactoring of PropertyHelper class was not applied since it may affect the other parts of the project.

@sonarqubecloud

Copy link
Copy Markdown

@zeynepatsoprasteria
zeynepatsoprasteria merged commit 83d51b1 into development Nov 10, 2026
8 checks passed
@zeynepatsoprasteria
zeynepatsoprasteria deleted the 426-generated-dto-comparers-treat-equal-floating-point-values-as-different-nearlyequal-not-negated branch November 10, 2026 12:57
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.

Generated DTO comparers treat equal floating-point values as different (NearlyEqual not negated)

2 participants