Yes 100%, but this goes much further. There's an imperative discussion we need to have regarding symbol exports. While their functionality seems promising in theory, there's a significant gap - the ability to merge. The way the current system is structured often results in unnecessary duplications.
Now, one might think, "Why not just rename the duplicated functions?" Well, that works up to a point. But when you're importing a symbol multiple times (imagine a card design with specific functionality), renaming doesn't solve the core issue. The function becomes redundant. When you try to eliminate the duplicate from the resources, all references in the second instance get lost in the process. This means that even though the function is essentially the same, its multiple instances cannot be treated as such.
Moreover, there's an inconsistency we need to highlight: the showSceneByNumber function. This functionality is available in the runtime but remains inaccessible in the API, causing further complications in addressing scenes with the same name (rendering them unaddressable in code as we only have showSceneNamed).
To summarize, the heart of the matter is mapping. Without a robust system to map and manage duplicates, we're left with a jumble that hinders efficiency and clean design. For a detailed dive into resolving this merging challenge, here's the feature request and discussion about the merge functionality: