Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


On this page:

Flex 1.1.1

Resolved issues

R&D IDTicket IDSummary
FLEX-13614266Unable to download extension via CLI. The specified path, file name, or both are too long.

Flex 1.1.0

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:
1003032Avoid unused variable (Flex)
1003046Avoid too short variable name (Flex)
1003052Avoid variable names ending with numeric characters (Flex)
1003060Avoid variable incorrectly named (Flex)
1003166Avoid using Object class in variables (Flex)
1003174Avoid * and use strongly typed objects instead in variables (Flex)
  • 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.
1003014Avoid nested if statement (Flex)
1003020Avoid empty method (Flex)
1003026Avoid complex methods (Flex)
1003030Avoid function with unused parameter (Flex)
1003054Avoid local variable hiding a class property (Flex)
1003056Avoid class name not starting by a majuscule character (Flex)
1003082Avoid instantiating variable in a loop (Flex)
1003088Avoid calling Alert.show directly (Flex)
1003110Avoid function that are too long (Flex)
1003126Avoid method with more than one exit point (Flex)
1003146Avoid call to callLater explicitly (Flex)
1003152Avoid DispatchEvent function not dispatching constant strings (Flex)
1003154Avoid addEventListener containing hard coded strings (Flex)

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:

R&D IDTicket IDSummaryComments
FLEX-7710507Missing links between Flex functions.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 links between Flex functions impacting rule results and function point values.
FLEX-10113921Flex warn: An unnamed object of type 'FLEX_script' has been detected.

When using previous releases of the extension, warnings were visible in the analysis log as follows:

An unnamed object of type 'FLEX_script' has been detected

This resulted in the creation of FLEX_Script objects with no name. This bug has now been fixed, therefore, after an upgrade to Flex 1.1.0 and the generation of a post upgrade snapshot on unchanged source code, results may differ: all FLEX_Script objects are now resolved correctly with their name and as such the existing unnamed objects will be reported as deleted and the objects now with names will be reported as newly added.

FLEX-10214008Analysis does not complete and is stuck processing a file.-
FLEX-107-No violations for "Avoid variable with too short name"This rule was not producing any violations. This bug has now been fixed, 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 for this rule.
FLEX-124-Flex extension does not detect functions that have names with 3 or less charactersFlex functions that have names with 3 characters or less are now correctly resolved as objects. 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 objects and potential for increased number of violations on these objects.
FLEX-125-An unnamed object is created when alias is given with single quote.

Aliases defined in code using single quote marks were being resolved as "unnamed" during the analysis - see code example below:

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

This bug has now been fixed, therefore after an upgrade to Flex 1.1.0 and the generation of a post upgrade snapshot on unchanged source code, results may differ: objects are now correctly resolved with their name when single quote marks are used.

FLEX-126-Unable to detect object end of Flex_Field

When using previous releases of the extension, sometimes it was not possible to detect the end of objects in the analyzed code. This resulted in:

  • objects such as FLEX Fields, Getters, Setters and Functions not being resolved
  • a warning in the analysis logs "Unable to detect object end for Flex_Field and Flex_Class"
  • incorrect bookmarks in code for rule violations.

This bug has been fixed and after an upgrade to Flex 1.1.0 and the generation of a post upgrade snapshot on unchanged source code, results may differ: object ends are detected correctly, thus increasing the number of objects detected and violations are correctly bookmarked in the code.

  • No labels