Skip to content

Commit

Permalink
Rename helper function to avoid confusion with React hook (#38340)
Browse files Browse the repository at this point in the history
Summary:
Pull Request resolved: #38340

changelog: [internal]

Reviewed By: yungsters

Differential Revision: D47437149

fbshipit-source-id: 32a9c4effa1a2ea2207d5cb85f0ffd7878110d11
  • Loading branch information
sammy-SC authored and facebook-github-bot committed Jul 13, 2023
1 parent fcfaf8c commit ec1e2af
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ export default function useAnimatedProps<TProps: {...}, TInstance>(
[props],
);
const useNativePropsInFabric =
ReactNativeFeatureFlags.useSetNativePropsInFabric();
ReactNativeFeatureFlags.shouldUseSetNativePropsInFabric();
useAnimatedPropsLifecycle(node);

// TODO: This "effect" does three things:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ export type FeatureFlags = {|
/**
* Enables use of setNativeProps in JS driven animations.
*/
useSetNativePropsInFabric: () => boolean,
shouldUseSetNativePropsInFabric: () => boolean,
|};

const ReactNativeFeatureFlags: FeatureFlags = {
Expand All @@ -64,7 +64,7 @@ const ReactNativeFeatureFlags: FeatureFlags = {
isGlobalWebPerformanceLoggerEnabled: () => false,
enableAccessToHostTreeInFabric: () => false,
shouldUseAnimatedObjectForTransform: () => false,
useSetNativePropsInFabric: () => false,
shouldUseSetNativePropsInFabric: () => false,
};

module.exports = ReactNativeFeatureFlags;

0 comments on commit ec1e2af

Please sign in to comment.