We found a work-around for the current issue for now.
That being said, it’s probably a good idea to look into upgrading when we’re
under less pressure.
Harbs
> On Nov 28, 2023, at 7:35 PM, Greg Dove wrote:
>
> I might be wrong, but I think from memory, there were some issues upgrading
> becau
I might be wrong, but I think from memory, there were some issues upgrading
because of the current state of support for runtime module loading, and
some changes in the GC classes that were subclassed in royale compiler
code. I think this was a blocker for easy upgrade in the past when I tried,
but
It could be as easy as updating the version number, and everything still
works the same from our end. Or they could have breaking changes in the
Closure Compiler APIs, or maybe they've started requiring JS to be written
in a different way, and then things could be very complicated.
--
Josh Tynjala
I guess I’ll try.
And IIRC, updating Closure Compiler was very complicated. Right?
> On Nov 28, 2023, at 6:46 PM, Josh Tynjala wrote:
>
> You can set the GOOG_HOME environment variable (or env.GOOG_HOME in
> env.properties) to use a custom Closure Library when building royale-asjs,
> instead of
You can set the GOOG_HOME environment variable (or env.GOOG_HOME in
env.properties) to use a custom Closure Library when building royale-asjs,
instead of the version that we have pinned.
I seem to remember Alex mentioning that updating either Closure Compiler or
Closure Library *sometimes* also re
It seems like our dependency of Closure Compiler is too old.
I have an app which runs inside Google Workspace and I’m having issues running
a debug version since Google enabled TrustedHTML
restrictions.https://developer.mozilla.org/en-US/docs/Web/API/TrustedHTML
The newer versions appear to sup
