That's great news! Related, I had understood that this didn't work at all, but I discovered via https://bugs.chromium.org/p/chromium/issues/detail?id=327092 that there is an "experimental" feature in chrome that lets locals be displayed. [image: screenshot867.png] However even with this enabled, only locals/params will show up with their correct names - any fields on those, or fields on "this" will still require finding their obfuscated names.
On Tuesday, December 12, 2023 at 9:47:40 AM UTC-6 Thomas Broyer wrote: > On Tuesday, December 12, 2023 at 3:44:34 PM UTC+1 [email protected] > wrote: > > Which limitation are you referring to? Is it something that can be fixed > or is it impossible to fix variable names there? > > > > https://ecma-international.org/news/ecma-tc39-ecmascript-initiates-a-new-task-group-to-standardize-source-maps/ > > The group’s plan is to identify the gaps, bring completeness and clarity > to the current specification; and help source map debuggers, generators and > tools to adhere to the updated specification. The intent is to work > together on *adding long requested features such as passing through > function and variable names*, and debug IDs to quickly identify source > files or scope information. > > (emphasis mine) > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a876be26-063e-4466-a5c5-5f5760293733n%40googlegroups.com.
