From 7d0b1c25d0c526b4856b0e25508015b9c50cc1fd Mon Sep 17 00:00:00 2001 From: Simon Holmes Date: Fri, 1 May 2026 10:27:37 +0100 Subject: [PATCH] chore: add changeset for #24 feature-flag defaults fix PR #25 (the implementation) was merged without a changeset, so the fix has not appeared in any release yet. This adds the missing changeset so the next release publishes the feature-flag fix. Co-Authored-By: Claude Opus 4.7 (1M context) --- .changeset/feature-flag-defaults.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 .changeset/feature-flag-defaults.md diff --git a/.changeset/feature-flag-defaults.md b/.changeset/feature-flag-defaults.md new file mode 100644 index 0000000..e84406d --- /dev/null +++ b/.changeset/feature-flag-defaults.md @@ -0,0 +1,7 @@ +--- +'@srsholmes/vitest-react-native': patch +--- + +Fix `ReactNativeFeatureFlags` mock missing own-properties (#24). + +The Proxy-only mock left every flag except `isLayoutAnimationEnabled` absent as an own-property, so named imports, `Object.keys`, and object spreads could miss `enableNativeCSSParsing` and the other ~100 flags. Now enumerates every flag from RN 0.83 with its real default (booleans, the numeric `preparedTextCacheSize`/`viewCullingOutsetRatio`/`virtualViewHysteresisRatio`/`virtualViewPrerenderRatio`, the string `virtualViewActivityBehavior`, and `override`). The Proxy fallback remains so flags added in future RN releases still degrade to `() => false`.