Fixed import type
circular references of NativeOrDynamicColorType
#154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please select one of the following
Description of changes
The previous Pull Request #146 renamed and moved the Flow type NativeOrDynamicColorType. It also created some circular references via the
import type
imports of this type. Flow itself seems to be able to handle these circular references, but an internal tool in Microsoft cannot. And these circular references are a bad practice.Created a new file, Libraries/Color/NativeOrDynamicColorType.js, that contains the
export type NativeOrDynamicColorType = ...
definition. Changed all theimport type {NativeOrDynamicColorType} from
instances to reference the new file.Microsoft Reviewers: Open in CodeFlow