I read that link, it's very helpful. It seems that this is going to be a challenge. I suggest you revert that as you suggested.
Josh discovered this originally for static accessors I think (the fact that @export does not prevent renaming on statics and @expose was the only other option that seemed to work). I 'rediscovered' it when I was working on static bindables. Then it became obvious it also affected static variables and methods when I tested for reflection. The advice in that note is similar to what I think you were mentioning elsewhere about string access. "If you want a property not to be obfuscated, access it as this['sample']instead of this.sample (you'll also need to fix all references)." (instead of using @expose) Go ahead and revert that change and I can see what (if anything) I can do with the above when I'm back. On Sat, Oct 1, 2016 at 6:53 AM, Greg Dove <greg.d...@gmail.com> wrote: > Alex, @export did not work for me on any static members. You cannot > reflect into the field names unless you use @expose. > > You can double check this via generictests reflection tests. > > -Greg > [sent from my phone] > > On 1/10/2016 5:21 AM, "Alex Harui" <aha...@adobe.com> wrote: > >> >> >> On 9/29/16, 11:36 PM, "Alex Harui" <aha...@adobe.com> wrote: >> > >> >Now that I got rid of the circularity in Ibead/Istrand I am also getting >> a >> >ton of warnings that say: >> > >> > WARNING - incomplete alias created for namespace goog >> >> I think is is being caused by the change from @export to @expose [1] >> >> What was the scenario where @export wasn't working? I'm going to switch >> things back to @export >> >> -Alex >> >> [1] https://developers.google.com/closure/compiler/docs/error-ref >> >>
