It is suggested to optimize the precision loss problem caused by numerical calculation and the null value processing mechanism in operation comparison #66
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.
Hello, author. Regarding the issue that operations in MathExpression may result in null values and other numbers being calculated, leading to rule validation failures, and the problem of precision loss due to the use of the double modifier, as well as the issue of comparing null values with numerical values resulting in null values, it is suggested to perform null checks during operations and judgments. As I am currently working on a project that requires the formulation of validation rules for reported data, the above-mentioned points are problems I have encountered during the project development. The author can consider optimizing these aspects. At the same time, I am very grateful for the tool provided by the author, which has saved a lot of development time.