> I can look into adding name mapping to our debug build source maps. That would be amazing!
> On Jul 22, 2024, at 6:17 PM, Josh Tynjala <joshtynj...@bowlerhat.dev> wrote: > > As I recall, the main thing that I focused on when implementing source maps > was ensuring that breakpoints worked properly. It is possible that the > Royale compiler renames some things, and we don't map the original AS3 > names to the generated JS names yet. (Generally, we try to keep the same > variable names in JS, but I recall that there are some special cases where > we rename). That's for debug builds. However, for release builds, source > maps are generated by Closure Compiler. I don't think that we have a lot of > control over how Closure Compiler generates source maps (nor could we take > over for it, since we wouldn't know the new names it generates for > variables and things). > > I can look into adding name mapping to our debug build source maps. > > -- > Josh Tynjala > Bowler Hat LLC <https://bowlerhat.dev> > > > On Sun, Jul 21, 2024 at 6:24 AM Gabe Harbs <harbs.li...@gmail.com> wrote: > >> I’ve never really tried debugging with source-maps enabled. I figured I’d >> give it a try and while cool, it doesn’t feel so useful because identifiers >> are not mapped to qualified names. >> >> That includes qualified names of classes and functions and even simple >> things like instance variables not being mapped to “this”. >> >> Is there any way around this limitation? What do other frameworks do? >> >> Harbs