On 1/19/17, 10:27 AM, "Josh Tynjala" <[email protected]> wrote:
>Is it only supported on classes? Is it possible to add it to variables or
>functions in packages too? As an example, I think something like this will
>be a common quick-and-dirty workaround for accessing JS globals.
>
>package
>{
> /**
> * @externs
> */
> public var myGlobal:Object;
>}
I didn't test it on anything other than a class. Feel free to try it and
maybe even fix it if it doesn't work.
I'm not sure I understand this particular use case though. If you are
accessing a third-party library, usually there is more than just a global
object in the APIs. Are you just trying to prevent renaming on something?
-Alex
