[pull] master from microsoft:master - #532
Merged
Merged
Conversation
## Previous Behavior * The indeterminate `<fluent-checkbox>` example wasn't wired up correctly. * The `<fluent-accordion>` example felt a bit separated. ## New Behavior * The `indeterminate` flag is set when the page is loaded. * The accordion example uses single expand mode.
## Previous Behavior The V2 → V3 migration guide (`packages/web-components/src/_docs/developer/migration.mdx`) was a high-level, snapshot-style document. It listed what was new in v3 as bullet points and relied heavily on large comparison tables, but gave little concrete guidance on how to actually update code — installation, component registration, theming, and per-component markup changes were sparse or missing. ## New Behavior The migration guide is rewritten to be a practical, task-oriented reference for moving from v2 (`2.6.1`) to v3: - Reframes the intro around v3 being a ground-up rewrite and calls out the concrete breaking areas: imports, component registration, theming, and form-control markup. - Adds a **Major Changes** overview (FAST Element v3 foundation, individual component exports, new registration model, token-based theming, `ElementInternals`, smaller bundle). - Adds a real **Bundle Size Comparison** table (v2.6.1 vs v3.0.0, with minified/gzip/brotli sizes and percentage reductions). - Adds **Usage** guidance covering installation, the `@microsoft/fast-element` peer dependency, side-effect `define` imports for individual components, `web-components.js`, and importing a component's class/template/styles/definition. - Documents the new **Theming** model, replacing design tokens and `DesignSystemProvider` with `setTheme()` (page-level and element-level, plus unsetting). - Updates the Storybook `Meta` title from "V2 → V3 Migration Guide" to "V2 to V3 Migration Guide" and the page heading to "Migration Guide".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )