Skip to content

Update and improve Data Mapper documentation#480

Merged
pasindufernando1 merged 9 commits into
wso2:mainfrom
KCSAbeywickrama:dm-review-update2
May 19, 2026
Merged

Update and improve Data Mapper documentation#480
pasindufernando1 merged 9 commits into
wso2:mainfrom
KCSAbeywickrama:dm-review-update2

Conversation

@KCSAbeywickrama
Copy link
Copy Markdown
Contributor

@KCSAbeywickrama KCSAbeywickrama commented May 18, 2026

Purpose

Focuses on the Data Mapper section under Other Artifacts.
refines the Data Mapper documentation for clarity, consistency, and accuracy.

Please review and merge #474 first, since this PR is built on top of it.

Summary by CodeRabbit

  • Documentation
    • Clarified Data Mapper workflows (array-to-array, array-to-single-value, one-to-one, nested/join mapping) and improved wording for mapping steps.
    • Standardized term formatting to “Sub Mappings” across guides.
    • Updated wording for expression editor/bar and type-generation from sample (Add Sample JSON/XML step).
    • Narrowed inline Data Mapper entry guidance to opening from Declare Variable nodes only.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 18, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f904d86f-adbf-4478-b8eb-82d77b64df09

📥 Commits

Reviewing files that changed from the base of the PR and between d520049 and 3926f07.

📒 Files selected for processing (10)
  • en/docs/develop/integration-artifacts/supporting/data-mapper/access-paths/access-paths.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/access-paths/inline.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/access-paths/reusable.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-array.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-single-value.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/data-mapper.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/generic-type-mappings.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/mapping-capabilities.md
  • en/docs/develop/understand-ide/editors/datamapper-editor.md
  • en/docs/develop/understand-ide/editors/flow-diagram-editor/statement.md
✅ Files skipped from review due to trivial changes (7)
  • en/docs/develop/integration-artifacts/supporting/data-mapper/access-paths/inline.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/access-paths/reusable.md
  • en/docs/develop/understand-ide/editors/flow-diagram-editor/statement.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-array.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/data-mapper.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-single-value.md
  • en/docs/develop/understand-ide/editors/datamapper-editor.md

📝 Walkthrough

Walkthrough

Documentation-only updates to Data Mapper pages: standardized "Sub Mappings" wording, clarified array mapping clause labels and nested/join instructions, narrowed inline entry points to Declare Variable, and aligned mapping/editor wording (expression bar/editor, selection workflows, "Map using" headings).

Changes

Data Mapper Feature Documentation

Layer / File(s) Summary
Standardize 'Sub Mappings' terminology
en/docs/develop/integration-artifacts/supporting/data-mapper/submappings.md
Replaced "Submappings"/"submapping" with "Sub Mappings"/"sub mapping" across frontmatter, headings, and body text.
Inline/reusable access-path entry point edits
en/docs/develop/integration-artifacts/supporting/data-mapper/access-paths/access-paths.md, .../inline.md, .../reusable.md
Updated inline and reusable access-path docs to state the Data Mapper is opened from a Declare Variable node only (removed Update Variable references).
Array mapping UI wording and clause labels
en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-array.md, .../array-to-single-value.md
Rewrote "Map each element" options to a human-readable "Clause Type" table; clarified "Nested iterate" and "Join with condition" sequencing; renamed and clarified array-to-single-value reduction option text and aggregation guidance; updated "What's next" label to "Sub Mappings".
Core overview, mapping workflows, and editor references
en/docs/develop/integration-artifacts/supporting/data-mapper/data-mapper.md, mapping-capabilities.md, generic-type-mappings.md, en/docs/develop/understand-ide/editors/datamapper-editor.md, flow-diagram-editor/statement.md
Removed the explicit Types prerequisite, harmonized "expression bar"/"expression editor" references, changed one-to-one mapping guidance to "select input then output field", added output-focused expression bar instructions and </> navigation guidance, retitled "Map with ..." to "Map using ...", required Add Sample JSON/Add Sample XML before pasting samples, and updated editor cross-reference capitalization/wording.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • pasindufernando1
  • rosensilva
  • anupama-pathirage
  • KavinduZoysa
  • NipunaRanasinghe

Poem

🐇 Hopping through docs to tidy each line,

Clauses and mappings now neatly align.
"Sub Mappings" gleam in consistent array,
Editor pointers guide the user's way.
A little rabbit cheers the doc-refresh day!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description only provides a brief Purpose section with minimal detail and lacks most required template sections like Goals, Approach, User Stories, Release Note, Documentation link, and others. Expand the description to include Goals explaining what clarity/consistency improvements are made, Approach with details on changes, and at least Documentation section with links to updated files or explanation of doc impact.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: documentation improvements and updates to the Data Mapper section, which aligns with all file changes in the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🧹 Nitpick comments (1)
en/docs/develop/integration-artifacts/supporting/data-mapper/submappings.md (1)

2-2: 💤 Low value

Consider renaming file to match the updated title.

The title was updated to "Sub Mappings" (two words), but the filename remains submappings.md. Per coding guidelines, spaces in titles should convert to hyphens in URLs, suggesting the file should be sub-mappings.md for consistency. However, if the existing filename is intentionally preserved for backward compatibility with existing links, this is acceptable.

Also applies to: 6-6

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@en/docs/develop/integration-artifacts/supporting/data-mapper/submappings.md`
at line 2, The document header uses the title "Sub Mappings" but the filename is
submappings.md; rename the file to sub-mappings.md to match the title-to-URL
convention (spaces → hyphens) and keep URLs/links consistent, or if
backward-compatibility is required, add a redirect/alias from submappings.md to
sub-mappings.md; update any references to the file name accordingly and verify
the title line ("title: Sub Mappings") remains unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/docs/develop/understand-ide/editors/datamapper-editor.md`:
- Line 74: The H2 header "Auto Map" should use sentence case per guidelines;
update the H2 text from "Auto Map" to "Auto map" (locate the header string "Auto
Map" in the datamapper-editor.md content and change only the capitalization).
- Line 48: Update the H3 header "Global Inputs" to sentence case by changing it
to "Global inputs" so it conforms to the project's header casing guideline;
locate the H3 line in datamapper-editor.md (the header text "Global Inputs") and
replace it with "Global inputs".
- Line 52: Update the H3 header text "Sub Mappings" to sentence case by changing
it to "Sub mappings" wherever the H3 appears (the header string "Sub Mappings"
in the datamapper-editor.md H3); ensure only the first word is capitalized and
proper nouns remain capitalized to comply with the sentence case guideline for
non-H1 headers.

---

Nitpick comments:
In `@en/docs/develop/integration-artifacts/supporting/data-mapper/submappings.md`:
- Line 2: The document header uses the title "Sub Mappings" but the filename is
submappings.md; rename the file to sub-mappings.md to match the title-to-URL
convention (spaces → hyphens) and keep URLs/links consistent, or if
backward-compatibility is required, add a redirect/alias from submappings.md to
sub-mappings.md; update any references to the file name accordingly and verify
the title line ("title: Sub Mappings") remains unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 93a5766c-13df-490f-b3db-049638babbad

📥 Commits

Reviewing files that changed from the base of the PR and between fb21e8b and d520049.

📒 Files selected for processing (8)
  • en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-array.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-single-value.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/data-mapper.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/generic-type-mappings.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/mapping-capabilities.md
  • en/docs/develop/integration-artifacts/supporting/data-mapper/submappings.md
  • en/docs/develop/understand-ide/editors/datamapper-editor.md
  • en/docs/develop/understand-ide/editors/flow-diagram-editor/statement.md

Comment thread en/docs/develop/understand-ide/editors/datamapper-editor.md
Comment thread en/docs/develop/understand-ide/editors/datamapper-editor.md
Comment thread en/docs/develop/understand-ide/editors/datamapper-editor.md
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates Data Mapper documentation for clearer terminology, UI flow descriptions, and current editor behavior across the Data Mapper guide and related editor pages.

Changes:

  • Refreshes Data Mapper Editor descriptions, header controls, expression bar, input/output sides, and mapping area behavior.
  • Updates Data Mapper capability pages for expression bar, generic sample generation, array mapping actions, and sub mapping terminology.
  • Adjusts cross-links and wording from related Flow Diagram editor documentation.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
en/docs/develop/understand-ide/editors/flow-diagram-editor/statement.md Updates the Data Mapper reference link wording from the Statement page.
en/docs/develop/understand-ide/editors/datamapper-editor.md Revises Data Mapper Editor overview, open paths, controls, expression bar, sides, and mapping area.
en/docs/develop/integration-artifacts/supporting/data-mapper/submappings.md Renames and rewords the Submappings page terminology.
en/docs/develop/integration-artifacts/supporting/data-mapper/mapping-capabilities.md Updates mapping interaction wording, expression bar details, and custom/transformation function labels.
en/docs/develop/integration-artifacts/supporting/data-mapper/generic-type-mappings.md Updates generic JSON/XML sample generation instructions.
en/docs/develop/integration-artifacts/supporting/data-mapper/data-mapper.md Updates overview wording, prerequisites, and capability naming.
en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-single-value.md Refines array-to-single-value mapping option descriptions.
en/docs/develop/integration-artifacts/supporting/data-mapper/array-mappings/array-to-array.md Updates array mapping clause labels and nested/join flow wording.

Comment thread en/docs/develop/understand-ide/editors/datamapper-editor.md Outdated
Comment thread en/docs/develop/understand-ide/editors/datamapper-editor.md
@pasindufernando1 pasindufernando1 merged commit b54b017 into wso2:main May 19, 2026
3 checks passed
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.

3 participants