Skip to content

feat(switch): update switch topics - #546

Open
Hristo313 wants to merge 13 commits into
vnextfrom
hhristov/update-switch-topics
Open

feat(switch): update switch topics#546
Hristo313 wants to merge 13 commits into
vnextfrom
hhristov/update-switch-topics

Conversation

@Hristo313

@Hristo313 Hristo313 commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Closes #537

Update the switch xplat topics

Also updated the samples:
Angular -> IgniteUI/igniteui-angular-samples#4025
React -> IgniteUI/igniteui-react-examples#1102
WC -> IgniteUI/igniteui-wc-examples#1254
Blazor -> IgniteUI/igniteui-blazor-examples#1302

Checklist:

  • check topic's TOC/menu and paragraph headings
  • Include TOC topic labels in the topic content when it has a valuable update, is new, or is considered preview / beta
  • link to other topics using ./page.mdx or ../relative/path.mdx (.mdx extension required)
  • at the References section at the end of the topic add links to topics, samples, etc
  • reference API documentation instead of adding a section with API

  • use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
  • use spell checker tool (VS Code, Grammarly, Microsoft Editor)
  • add inline code blocks for the names of classes / tags / properties
  • add language descriptor for the code blocks
  • check if links function by running the check-api/mdx npm commands
  • check if sample is working and fully visible in the topic
  • check if sample is working and fully visible in the StackBlitz
  • check if code blocks match the code in StackBlitz demo
  • add or update meaningful llms.description metadata and run npm run check:llms-metadata


  • do not resolve requested changes (leave that to the reviewer)

@ChronosSF ChronosSF added 💥 status: in-test PRs currently being tested and removed ❌ status: awaiting-test PRs awaiting manual verification labels Sep 4, 2026

### Prerequisites and Version Compatibility

Use a supported version of the {ProductName} package for your target framework. Keep the framework package, the Switch package, and the theme package on the same release version.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same comment as for the button - there isn't a separate switch package

<PlatformBlock for="React,WebComponents,Blazor">

<DocsAside type="warning" title="Warning">
The <ApiLink pkg="core" type="Switch" /> component doesn't work with the standard `<form>` element. Use `Form` instead.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know what that Form is... This needs a link or an elaboration. My guess is that it's actually a Blazor only note.

npm install igniteui-angular
```

Then import the `IgxSwitchModule` in an NgModule application, or import the `IgxSwitchComponent` as a standalone dependency:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like with button this is talking about modules but is importing the component.

@Hristo313
Hristo313 requested a review from ChronosSF September 8, 2026 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update switch topics

3 participants