[FLEX-26554] Refactor the logic of ensuring the style parent and the logic of checking locale style

• Type: Task
• Status: Closed
• Priority: Trivial
• Resolution: Later
• Affects Version/s: Adobe Flex SDK 4.5 (Release)
• Component/s: i18n : Formatter Support
• Environment: Affected OS(s): All OS Platforms; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 25/Jan/11 10:11
• Updated: 10/May/11 13:48
• Resolved: 25/Jan/11 10:12

Description

This is about refactoring the code and is not about fixing bug nor enhancing a feature.

In the globalizaiton-related Flex SDK Spark classes (such as Spark NumberFormatter, StringTools and so on), there are some logic of ensuring the style parent and the logic of checking locale style. Because those logics are introduced at the different time during its development, the way they interact may not be optimal. For example, once the style source is confirmed, is it necessary to check if locale style is undefined?

Investigate the code and work on refactor if necessary.

I suggest to work on this after the Hero release.

Steps to reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Workaround (if any):