no compiler arguments mention in doc or readme

[katopz]

in RL's doc (as i remember) it has

-keep-as3-metadata+=Inject -keep-as3-metadata+=PostConstruct

in some random thread e.g. http://knowledge.robotlegs.org/discussions/examples/870-modules-signals i found someone mention to use

-keep-all-type-selectors

in some case...so it no need compiler arguments anymore or need in some case?

Thanks

[Ondina]

They are 2 different things:

1- keep-all-type-selectors=true|false

Instructs the compiler to keep a style sheet's type selector in a SWF file, 
even if that type (the class) is not used in the application. 
This is useful when you have a modular application that loads other applications. 
For example, 
the loading SWF file might define a type selector for a type used in the loaded ( or, target ) SWF file. 
If you set this option to true when compiling the loading SWF file, 
then the target SWF file will have access to that type selector when it is loaded. 
If you set this option to false, 
the compiler will not include that type selector in the loading SWF file 
at compile time. 
As a result, the styles will not be available to the target SWF file.

2- keep-as3-metadata=class_name [...]

Specifies custom metadata that you want to keep. 
By default, the compiler keeps the following metadata:
• Bindable 
• Managed 
• ChangeEvent 
• NonCommittingChangeEvent 
• Transient 
If you want to preserve the default metadata, 
you should use the += operator to append your custom metadata, 
rather than the = operator which replaces the default metadata.

https://github.com/robotlegs/robotlegs-framework/wiki/Common-Problems#wiki-metadata-stripping

keep-all-type-selectors = true has no effect on the metadata.

[katopz]

Many Thanks!