[🐛 BUG] Mismatch between bound variable type and Pylance

[HoseynAAmiri]

What went wrong? 🤔

There is a type checking error from Pylance as I use binding:

tgb.selector(
    value="{selected_subcategory}",
    lov="{subcategories}",
    dropdown=True,
)

Argument of type "Literal['{subcategories}']" cannot be assigned to parameter "lov" of type "dict[str, Any] | None" in function "init"
Type "Literal['{subcategories}']" is not assignable to type "dict[str, Any] | None"
"Literal['{subcategories}']" is not assignable to "dict[str, Any]"
"Literal['{subcategories}']" is not assignable to "None"

And even without binding something like:

tgb.selector(
    value="{selected_subcategory}",
    lov=['x', 'y', 'z'],
    dropdown=True,
)

Argument of type "list[str]" cannot be assigned to parameter "lov" of type "dict[str, Any] | None" in function "init"
Type "list[str]" is not assignable to type "dict[str, Any] | None"
"list[str]" is not assignable to "dict[str, Any]"
"list[str]" is not assignable to "None"

So, it only accepts an lov type of dict[str, Any] that does not even work!

Additional Context

Acceptance Criteria

• A unit test reproducing the bug is added.
• Any new code is covered by a unit tested.
• Check code coverage is at least 90%.
• The bug reporter validated the fix.
• Related issue(s) in taipy-doc are created for documentation and Release Notes are updated.

Code of Conduct

• I have checked the existing issues.
• I am willing to work on this issue (optional)

[FlorianJacta]

Thank you; this issue is interesting as Taipy uses different ways to bind variables. The nature of the bound variable can be different from what Pylance sees. In your example, you pass a list of string (as a bound variable) but Pylance sees a string. The second use case is another issue that could be quickly solved