Brighterscript shows some "slightly helpful" completions after the callfunc operator. However, those values aren't deduped. We should only show distinct method names.
This can be fixed by tweaking the code here to build the callfunc completions into its own array, deduping them, and then adding them to the final event.completions array.
Add another unit test like this one that has multiple functions with the same name across multiple components, and make sure only a single completion for each name is returned.
Brighterscript shows some "slightly helpful" completions after the callfunc operator. However, those values aren't deduped. We should only show distinct method names.
This can be fixed by tweaking the code here to build the callfunc completions into its own array, deduping them, and then adding them to the final
event.completions
array.Add another unit test like this one that has multiple functions with the same name across multiple components, and make sure only a single completion for each name is returned.