Skip to content

fix(dialog): update topics content and assets - #939

Open
Hristo313 wants to merge 2 commits into
vnextfrom
hhristov/update-dialog-topics
Open

Hristo313 wants to merge 2 commits into
vnextfrom
hhristov/update-dialog-topics

Conversation

@Hristo313

Copy link
Copy Markdown
Contributor

Closes #743

Update the Dialog xplat topics

Also updated the samples:
Angular -> IgniteUI/igniteui-angular-samples#4058
React -> IgniteUI/igniteui-react-examples#1128
WC -> IgniteUI/igniteui-wc-examples#1303
Blazor -> IgniteUI/igniteui-blazor-examples#1333

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

notifications/dialog.mdx

2 participants