Project

General

Profile

Actions

Bug #22126

closed

Windows generic method parameters are always written "mandatory=true" even when "mayBeEmpty"

Added by François ARMAND almost 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No

Description

If we have a technic parameter than can be "MayBeEmpty" in the editor, it is actually mandatory not empty when used.

If we look at the generated code for the technique with such a parameter, we see that the parameter is written mandatory=$true when we would expect a false there.



Files

Actions

Also available in: Atom PDF