Bug? Should a local enum take precedence over a module?

I have this code, and it doesn't work in SDK 8.1.0:

The problem is that it thinks that Menu is WatchUi.Menu.

This causes a compilation error (at least with typecheck set to strict) because I want to assign something that is not an Action to action. This is relatively OK, though IMHO it shouldn't happen.

It also causes an unexpected behavior when running (of course it needs some changes so it compiles, or disabling typecheck):

In the switch action will never be equal to Menu (again because an Action is never equal to a module or class.

The workaround is to replace Menu with self.Menu. However I think this is a bug, and the compiler should have found the local Menu before it looks for the more remote WatchUi.Menu.

Should I open a bug report, or am I mistaken and this is how it's supposed to work?

flocsy🤠 16 days ago

https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-compiler-uses-module-instead-of-local-enum-value

flocsy🤠 16 days ago in reply to jim_m_58

jim_m_58 said:
reusing the same name

I disagree. In this file I did not use WatchUi.Menu. It's not reusing. Actually imagine if you had a watchface app from 3 years ago with something called WatchFaceConfig. When you upgraded to SDK 8 then your code became worse than it was, because now your code is reusing Application.WatchFaceConfig? Or is it Garmin reusing your class name? ;)

flocsy🤠 16 days ago in reply to FlowState

FlowState said:
not using title case for enums would avoid the problem altogether

Of course not, it would just mask the bug. Or can't I have an enum value called KEY_LEFT ? :)