(rosetta) type inference is not sufficiently narrowed causing incorrect Python translations

[nija-at]

🐛 Bug Report

Given the method signature -

mymethod(props: any);

and the snippet that uses this method as -

mymethod({
   Foo: 'Bar',
   Baz: 5
});

This gets incorrectly translated into Python as -

mymethod(
  Foo="Bar",
  Baz=5
)

Real life example -

================= 95964378aeaa3097f169ababbfa7299d423f35d782742e0b6ef0ec429f7e6e7e =================
template.hasResourceProperties('Foo::Bar', {
  Foo: 'Bar',
  Baz: 5,
  Qux: [ 'Waldo', 'Fred' ],
});
----------- python -----------
template.has_resource_properties("Foo::Bar",
    Foo="Bar",
    Baz=5,
    Qux=["Waldo", "Fred"]
)

[nija-at]

The workaround is to declare the second parameter as a separate variable with an explicit type before passing it into the method.

[RomainMuller]

Yeah so for some reason that last parameter seems interpreted as a property bag, whereas the type signature of the method suggests it cannot be that (it should only happen if the last parameter is known to be a struct).

[rix0rrr]

Oh this is fun. The type of this argument is any, but from the type checker PoV it doesn't (can't?) distinguish between an any that's declared as an any, or an any it just assumes because it can't find a declaration for a function, for example.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.