This is an automated email from the ASF dual-hosted git repository.
aharui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new c3e86c1 Updated Public Variables (markdown)
c3e86c1 is described below
commit c3e86c17a8d0fc257b11fa7d8240aff2fb85732f
Author: aharui <[email protected]>
AuthorDate: Tue Feb 20 09:46:18 2018 -0800
Updated Public Variables (markdown)
---
Public-Variables.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Public-Variables.md b/Public-Variables.md
index 21c1ec7..23668b1 100644
--- a/Public-Variables.md
+++ b/Public-Variables.md
@@ -13,7 +13,7 @@ If an application works in js-debug but not js-release,
public variables are oft
We are still learning more about other scenarios that may fail in js-release
due to renaming, so we may find that public variables always have to be
rewritten as getter/setter.
-The compiler has an option "-warn-public-vars" that is on by default. A
warning message will be in the compiler output. The framework code should
compile without these warnings. Either convert the var to getter/setter or
suppress the warning via the @royalesuppresspublicvarwarning ASDoc directive.
The directive can be used on each var or applied to an entire class.
+The compiler has an option "-warn-public-vars" that is on by default. A
warning message will be in the compiler output. The framework code should
compile without these warnings. Either convert the var to getter/setter or
suppress the warning via the @royalesuppresspublicvarwarning ASDoc directive.
The directive can be used on each var or applied to an entire class. public
vars with [Bindable] are exempt and should not cause the output of a warning
because [Bindable] instructs the co [...]
If a class is found to be at fault in js-release, check to see if
@royalesuppresspublicvarwarning is used in the class and consider whether the
renaming is at fault.
--
To stop receiving notification emails like this one, please contact
[email protected].
