1.1.3-funcrel

Other Updates

1.1.2-funcrel

Resolved issues

Updates

Improved analysis support

Analysis support has been been improved for certain Flex objects:

• getter/setter/functions
• member variables
• classes

Therefore after an upgrade to this version of the extension and the generation of a post-upgrade consistency snapshot, analysis results may be impacted: there may be an increase in the number of objects identified during the analysis and as a consequence, there may be impacts with regard to the violations detected for these Flex objects.

Related issues

• FLEX-162 - Improved detection of gettter\setter\functions
• FLEX-163 - Improved detection of member variables
• FlEX-164 - Improved detection of Flex classes

Reduced number of "UA Plugin: No Property found…" warnings

Changes have been made to reduce the warnings of type "UA Plugin: No Property found…". These changes will result in the following two impacts after an upgrade to this version of the extension and the generation of a post-upgrade consistency snapshot:

• Some of the Flex rules may have new violations
• The following rules will show all violations removed and then added back again because the violation object type has changed:
  • 1003198: Avoid MXML component with more than one entry point (Flex)
  • 1003200: Avoid MXML component with more than two entry points (Flex)

Flex Rules Updates

The documentation of all Flex rules has been updated. As part of the update, rule titles have been updated as shown in the table below:

1.1.1-funcrel

Resolved issues

1.1.0-funcrel

Updates

• New object icons have been introduced. See Flex 1.1.
• FLEX-91 - In previous releases of the extension, local variables in the source code were resolved as "FLEX Variable" objects. This behaviour has now been changed and FLEX Variable objects are no longer resolved. Therefore, after an upgrade to Flex 1.1.0 and the generation of a post upgrade snapshot on unchanged source code, results may differ. In addition, the following rules included FLEX Variable objects in their scope and have been modified to use FLEX Getter, Setter, Function and Script objects instead of FLEX Variables. There will be no impact on the number of violations for these rules:

• FLEX-77 - In previous releases of the extension, call links between Flex functions were never resolved, by design. This behaviour has now been changed and links between Flex functions are resolved.
• FLEX-127 - The use of the $ sign in the names of functions, fields, getters and setters is now supported and the object will be fully resolved. For example:

package {

public class DollarInName {
	mx_internal function get $transform() : int {
	return 0;
	}
	mx_internal function set $transform(int val) : void {
	}
	mx_internal function $transformThat() : void {
	}
}
}

• FLEX-133 - The RemoteObject parameter is now resolved correctly as an object. For example, in the following code, all RemoteObject parameters will be resolved:

<?xml version="1.0" encoding="utf-8"?>

<s:ProxyFactory xmlns:fx="http://ns.adobe.com/mxml/2009" 
		  xmlns:s="library://ns.adobe.com/flex/spark" 
		  xmlns:mx="library://ns.adobe.com/flex/mx"
		  xmlns:comp="com.att.ntscp.view.component.*" width="99%"  
		  >

  <mx:RemoteObject id="SingleStatementMultiline1"
	named="something"
	showBusyCursor="true"/>
	
	
		<mx:RemoteObject id="MultilineMultiline1" destination="helpDest" showBusyCursor="true">
			<mx:method name="setAttUid"/>
			<mx:method name="getCommandHelp"  result="onResult(event)" fault="onFault(event)"/>
		</mx:RemoteObject>
	

  <mx:RemoteObject id="SingleStatementSingleline1" named="something" showBusyCursor="true"/>
	
		<mx:RemoteObject id="MultilineMultiline2CommentInBetween" destination="helpDest" showBusyCursor="true">
			<mx:method name="setAttUid"/>
			<!-- no comment! -->
			<mx:method name="getCommandHelp"  result="onResult(event)" fault="onFault(event)"/>
		</mx:RemoteObject>
	
	
  <mx:RemoteObject id="SingleStatementMultiline2" named="something"
	showBusyCursor="true"/>
	
  <mx:RemoteObject id="SingleStatementMultiline2CommentBetweenLines" 
	named="something"
	showBusyCursor="true"/>
	
</s:ProxyFactory>

• FLEX Getter and Setter objects (new in Flex 1.1.0) will now be included in the scope for violations in the following rules, therefore, after an upgrade to Flex 1.1.0 and the generation of a post upgrade snapshot on unchanged source code, results may differ: increased number of violations providing improved accuracy.

Resolved issues

The Flex 1.1.0 contains all bug fixes from previous releases. The following table lists all bugs fixed in Flex 1.1.0 and that are not already fixed in the previous released versions:

An unnamed object of type 'FLEX_script' has been detected

[RemoteClass(alias='example.src.com.company.service.Device')]