Consolidate getCurrentAppearance, isHighContrast and setHighContrast in design package (#4155)

* move theming types into a subdirectory

* remove caching from prebuild step

* add theming platform utilities to the design package

* switch usage of theming utilities to the design package

* add changeset

* update dead links and add instructions to fix links

Author: JasonVMo

.changeset/odd-taxis-do.md

@@ -0,0 +1,21 @@
+---
+"@uifabricshared/theming-ramp": patch
+"@fluentui-react-native/android-theme": patch
+"@fluentui-react-native/default-theme": patch
+"@fluentui-react-native/theming-utils": patch
+"@fluentui-react-native/experimental-shimmer": patch
+"@fluentui-react-native/theme-tokens": patch
+"@fluentui-react-native/checkbox": patch
+"@fluentui-react-native/apple-theme": patch
+"@fluentui-react-native/theme-types": patch
+"@fluentui-react-native/tablist": patch
+"@fluentui-react-native/avatar": patch
+"@fluentui-react-native/button": patch
+"@fluentui-react-native/switch": patch
+"@fluentui-react-native/badge": patch
+"@fluentui-react-native/menu": patch
+"@fluentui-react-native/theme": patch
+"@fluentui-react-native/design": patch
+---
+
+Move platform theming utilities into the design package, update usage in the repo to use the new source"

AGENTS.md

@@ -71,6 +71,7 @@ yarn format:check  # Check formatting without writing
 ```bash
 yarn lint-repo        # Repo-wide structural lint (scripts/src/tasks/lintRepo.ts)
 yarn lint-lockfile    # Validate the Yarn lockfile
+yarn lage test-links # Validate links in repository Markdown files
 yarn check-publishing # Validate package publishing configuration
 yarn change           # Create a change file for the current branch
 yarn change:check     # Verify required change files exist
@@ -85,6 +86,7 @@ The task pipeline is defined in `lage.config.mjs`:
 - `buildci` is the aggregate CI alias (lint-repo, check-publishing, build, test, lint)
 - Lage caches task outputs; add `--no-cache` to bypass caching and `--verbose` for detailed output
 - After a major rework (e.g. moving packages, large refactors, or renaming exports), run `yarn lage test --no-cache` from the root once to force every test to re-run without relying on stale cached results. This also resets the Lage cache, so subsequent plain `yarn lage test` runs will work incrementally again.
+- Before checking in moved or renamed files, run `yarn lage test-links` and update any repository links that still reference the old paths.
 
 ### Package-Level Commands
 

apps/tester-core/package.json

@@ -73,7 +73,6 @@
     "@fluentui-react-native/theme": "workspace:*",
     "@fluentui-react-native/theme-tokens": "workspace:*",
     "@fluentui-react-native/themed-stylesheet": "workspace:*",
-    "@fluentui-react-native/theming-utils": "workspace:*",
     "@fluentui-react-native/tooltip": "workspace:*",
     "@fluentui-react-native/vibrancy-view": "workspace:*",
     "@fluentui-react-native/win32-theme": "workspace:*",

apps/tester-core/src/TestComponents/ColorTokens/ColorTokenTest.tsx

@@ -10,7 +10,7 @@ import { globalTokens } from '@fluentui-react-native/theme-tokens';
 import type { Theme } from '@fluentui-react-native/design/theming';
 import { useTheme } from '@fluentui-react-native/design/theming';
 import { themedStyleSheet } from '@fluentui-react-native/themed-stylesheet';
-import { getCurrentAppearance } from '@fluentui-react-native/theming-utils';
+import { getCurrentAppearance } from '@fluentui-react-native/design/theming';
 import { createOfficeAliasTokens } from '@fluentui-react-native/win32-theme';
 import type { SvgProps } from 'react-native-svg';
 import Svg, { G, Path } from 'react-native-svg';

apps/tester-core/src/TestComponents/CornerRadius/CornerRadiusTest.tsx

@@ -16,7 +16,7 @@ import { Text } from '@fluentui/react-native';
 import { HOMEPAGE_CORNERRADIUS_TESTPAGE } from '@fluentui-react-native/e2e-testing';
 import { useFluentTheme } from '@fluentui-react-native/framework';
 import { Stack } from '@fluentui-react-native/stack';
-import { getCurrentAppearance } from '@fluentui-react-native/theming-utils';
+import { getCurrentAppearance } from '@fluentui-react-native/design/theming';
 
 import { stackStyle } from '../Common/styles';
 import type { TestSection, PlatformStatus } from '../Test';

apps/tester-core/src/TestComponents/StrokeWidth/StrokeWidthTest.tsx

@@ -19,7 +19,7 @@ import type { Theme } from '@fluentui-react-native/framework';
 import { useFluentTheme } from '@fluentui-react-native/framework';
 import { Stack } from '@fluentui-react-native/stack';
 import { themedStyleSheet } from '@fluentui-react-native/themed-stylesheet';
-import { getCurrentAppearance } from '@fluentui-react-native/theming-utils';
+import { getCurrentAppearance } from '@fluentui-react-native/design/theming';
 
 import { stackStyle } from '../Common/styles';
 import type { TestSection, PlatformStatus } from '../Test';

apps/tester-core/tsconfig.json

@@ -145,9 +145,6 @@
     {
       "path": "../../packages/framework/themed-stylesheet/tsconfig.json"
     },
-    {
-      "path": "../../packages/theming/theming-utils/tsconfig.json"
-    },
     {
       "path": "../../packages/experimental/Tooltip/tsconfig.json"
     },

docs/pages/Theming/CustomTheme.md

@@ -8,7 +8,7 @@ There are two ways to make a custom theme: you can tack onto an existing one usi
 
 ### Extending an existing `ThemeReference`
 
-We have a concept of `ThemeRecipes` which allow for layering of partial theme objects to create the ultimately desired theme. `ThemeRecipes` are functions which take a `Theme` and spit out a [`PartialTheme`](../../../packages/agentic-design/src/theming/Theme.types.ts), which is then deep merged into the base theme object.
+We have a concept of `ThemeRecipes` which allow for layering of partial theme objects to create the ultimately desired theme. `ThemeRecipes` are functions which take a `Theme` and spit out a [`PartialTheme`](../../../packages/agentic-design/src/theming/types/Theme.types.ts), which is then deep merged into the base theme object.
 
 You can extend one of our default themes by creating a `ThemeReference` using the default theme as the base theme, and then add your customization as a `ThemeRecipe`:
 
@@ -46,7 +46,7 @@ There's two ways to customize a FURN theme's properties:
 
 ### Changing theme tokens directly
 
-Theme tokens can be overridden directly. You can specify different values for theme entries and add to the set of colors. You can see what can be overridden by looking at the [Theme type definition](../../../packages/agentic-design/src/theming/Theme.types.ts).
+Theme tokens can be overridden directly. You can specify different values for theme entries and add to the set of colors. You can see what can be overridden by looking at the [Theme type definition](../../../packages/agentic-design/src/theming/types/Theme.types.ts).
 
 This approach is useful if you need the customizations to be applied to all components.
 
@@ -161,7 +161,7 @@ interface Theme {
 }
 ```
 
-<font size=1>(Taken from the [`Theme` type definition](../../../packages/agentic-design/src/theming/Theme.types.ts).)</font>
+<font size=1>(Taken from the [`Theme` type definition](../../../packages/agentic-design/src/theming/types/Theme.types.ts).)</font>
 
 NOTE: If you would prefer to customize one instance of a FURN component instead, use [the customize API](../../../packages/framework/composition/README.md).
 

docs/pages/Theming/Tokens/Basics.md

@@ -74,7 +74,7 @@ export const defaultNotificationTokens: TokenSettings<NotificationTokens, Theme>
 
 Notes about alias color tokens:
 
-- Different platforms can have different sets of alias tokens; however, the entire set of alias tokens are all defined in the same interface. See [Color.types.ts](https://github.com/microsoft/fluentui-react-native/blob/main/packages/agentic-design/src/theming/Color.types.ts#L861) for this interface and which platforms define which alias tokens.
+- Different platforms can have different sets of alias tokens; however, the entire set of alias tokens are all defined in the same interface. See [Color.types.ts](../../../../packages/agentic-design/src/theming/types/Color.types.ts#L861) for this interface and which platforms define which alias tokens.
 - As a result, if an alias token is referenced that does not exist for that platform, there won't be any compile-time or run-time errors. Instead, the color shown will default to black.
 
 Special case: if accessing a specific color, you can find it in the `globalTokens.color` property.

lage.config.mjs

@@ -49,8 +49,7 @@ const config = {
        * Prebuild is a pre-build step that can either modify the source code or generate additional files in the project.
        */
       dependsOn: ['^prebuild'],
-      inputs: ['**/*', '!node_modules/**/*', '!dist/**/*', '!lib/**/*', '!lib-commonjs/**/*'],
-      outputs: ['lib/**/*', 'src/**/*'],
+      cache: false,
     },
     'root-prebuild': {
       cache: false,