[
https://issues.apache.org/jira/browse/FLEX-34880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihai Chira updated FLEX-34880:
-------------------------------
Description: (Both mx and spark) {{Sort}} and {{SortField}} will be
transitioned to immutable objects to prevent bugs like FLEX-34853. In this step
we're hiding the state setters behind the {{mx_internal}} namespace. This also
implies renaming them (because a getter and a setter with different namespaces
throws a compile error). The pattern is: {{public function set
compareFunction(c:Function):void}} becomes {{mx_internal function set
compareFunction_(c:Function):void}}. (was: This is the second step of fixing
FLEX-34853.)
> Place Sort and SortField state setters behind mx_internal
> ---------------------------------------------------------
>
> Key: FLEX-34880
> URL: https://issues.apache.org/jira/browse/FLEX-34880
> Project: Apache Flex
> Issue Type: Sub-task
> Components: Spark: Sort and SortField
> Affects Versions: Apache Flex 4.15.0
> Reporter: Mihai Chira
> Assignee: Mihai Chira
> Fix For: Apache Flex 4.16.0
>
>
> (Both mx and spark) {{Sort}} and {{SortField}} will be transitioned to
> immutable objects to prevent bugs like FLEX-34853. In this step we're hiding
> the state setters behind the {{mx_internal}} namespace. This also implies
> renaming them (because a getter and a setter with different namespaces throws
> a compile error). The pattern is: {{public function set
> compareFunction(c:Function):void}} becomes {{mx_internal function set
> compareFunction_(c:Function):void}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
