Skip to content

docs: update Japanese row drag topic - #475

Open
mkamiishi wants to merge 1 commit into
vnextfrom
docs/update-ja-row-drag
Open

docs: update Japanese row drag topic#475
mkamiishi wants to merge 1 commit into
vnextfrom
docs/update-ja-row-drag

Conversation

@mkamiishi

Copy link
Copy Markdown
Contributor

Summary

Updated the Japanese Row Drag documentation to better align with the current English source.

Changes

  • Updated untranslated Japanese Row Drag content based on the English source.
  • Removed duplicated or outdated English text from the Japanese topic.
  • Added missing translated descriptions for row drag UX scenarios.
  • Preserved code snippets, component names, property names, and event names.

Testing

  • Compared the Japanese Row Drag topic with the English source.
  • Ran markdownlint for the updated MDX file.
  • Confirmed that code snippets, component names, property names, and event names are preserved.

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)

@IG-Mori
IG-Mori self-requested a review July 31, 2026 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant