Fixed several issues related to number handling and wildcard processing

[izmp]

Summary

Fixed several issues related to number handling and wildcard processing in the YAML files and ImpactWildcardProcessor. Verified and tested on build v8.6.0.

Note

This pull request message was generated with the help of Copilot translation due to language limitations. Thank you for your understanding.

Fixes

• Resolved probability calculation errors when using large numbers in n2.

• Fixed issue where n1-$$ is not supported.

• Addressed issue Using separator, wildcards and multi-selection in ImpactWildcardProcessor only selected a single result from wildcard #873 where using separators, wildcards, and multi-selection in ImpactWildcardProcessor only selected a single result from wildcard.

• Corrected error where YAML number values caused incorrect string representations.

Related Issues

#873

Detailed Explanation

Probability using large numbers in n2

{1-9999999$$0|1|2|3}
  expected probability:
   25% = length 1 (0 or 1 or..):
   25% = length 2 (01 or 12 or...):
   25% = length 3 (012 or 123 or ...):
   25% = length 4 (0123 or 1230 or...):
  actual probability:
   0% = length 1 (0 or 1 or..):
   0% = length 2 (01 or 12 or...):
   0% = length 3 (012 or 123 or ...):
   99% = length 4 (0123 or 1230 or...):

n1-$$ is not supported

{1-$$0|1|2|3}
  expected probability:
   25% = length 1 (0 or 1 or..):
   25% = length 2 (01 or 12 or...):
   25% = length 3 (012 or 123 or ...):
   25% = length 4 (0123 or 1230 or...):
  actual probability:
   100% = length 1 (0 or 1 or..):
   0% = length 2 (01 or 12 or...):
   0% = length 3 (012 or 123 or ...):
   0% = length 4 (0123 or 1230 or...):

Issue #873 - Using separator, wildcards, and multi-selection in ImpactWildcardProcessor

{1-3$$sep$$<wildcard>}
  expected probability:
   33% = length 1 (0 or 1 or..):
   33% = length 2 (01 or 12 or...):
   33% = length 3 (012 or 123 or ...):
  actual probability:
   100% = length 1 (0 or 1 or..):
   0% = length 2 (01 or 12 or...):
   0% = length 3 (012 or 123 or ...):

YAML number value causes error

# .yaml
  numberonly:
    # Value should be a string, numbers result in incorrect strings
    type_int:
      - 0
      - 1
    # Value should be a string, numbers result in incorrect strings
    type_int2: 0
    type_int3: 1
    # "0", "1" is correct value
    type_str:
      - |-
        0
      - |-
        1
    type_str2: "1"

Testing

• Verified probability calculations are now accurate with various number ranges.

• Confirmed that n1-$$ is now supported as expected.

• Tested ImpactWildcardProcessor with multiple scenarios involving separators, wildcards, and multi-selection to ensure correct results.

• Checked YAML files to confirm number values are correctly processed as strings.