Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: The DeepPartialV2 type is used in mergeStyles but not exported from index #33805

Open
2 tasks done
gyz0072004 opened this issue Feb 10, 2025 · 0 comments · May be fixed by #33806
Open
2 tasks done

[Bug]: The DeepPartialV2 type is used in mergeStyles but not exported from index #33805

gyz0072004 opened this issue Feb 10, 2025 · 0 comments · May be fixed by #33806

Comments

@gyz0072004
Copy link
Member

Package

merge-styles

Package version

8.6.13

React version

17.0.2

Environment

System:
    OS: Windows 11 10.0.26100
    CPU: (16) x64 AMD EPYC 7763 64-Core Processor
    Memory: 39.63 GB / 63.95 GB
  Browsers:
    Edge: Chromium (129.0.2792.65)
    Internet Explorer: 11.0.26100.1882

Current Behavior

The DeepPartialV2 is not exported from the index of mergeStyles package (can only import {DeepPartial} from '@fluentui/merge-styles' but not import {DeepPartialV2} from '@fluentui/merge-styles'). As the deprecated DeepPartial will cause infinite ts issue, fluentui should at least export the DeepPartialV2 for usage.

Expected Behavior

DeepPartialV2 is exported from merge-styles

Reproduction

https://stackblitz.com/edit/vitejs-vite-cbctgyu2?file=src%2Fmain.ts

Steps to reproduce

  1. Go to main.ts
  2. Replace DeepPartial with DeepPartialV2
  3. The import is not identified

Are you reporting an Accessibility issue?

None

Suggested severity

Medium - Has workaround

Products/sites affected

No response

Are you willing to submit a PR to fix?

yes

Validations

  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant