Fix: Remove automatic input and output mapping generation statements [main]

[wso2-engineering-bot]

This PR was automatically generated by Claude AI.

• Issue: Remove Automatic Input and Output Mapping Generation statement in dataservices docs. #1910
• Type: Documentation
• Summary: Removed statements about automatic generation of input and output mappings from SQL queries in the data services documentation as they are no longer valid.
• Style Scope Verification: Microsoft Style Guidelines have been applied only to newly added content without modifying existing content style unless specifically requested.
• Verification: mkdocs build passed successfully

Summary by CodeRabbit

• Documentation
  • Restructured data services documentation to provide explicit, step-by-step guidance for manually creating input and output mappings. Documentation previously described optional approaches; guidance is now consolidated around manual configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This update modifies documentation for data service creation, replacing sections describing optional mapping approaches with explicit step-by-step procedures for manually creating input and output mappings.

Changes

Cohort / File(s)	Summary
Documentation Updates en/docs/develop/creating-artifacts/data-services/creating-data-services.md	Replaced optional mapping creation approaches with explicit manual procedures; removed references to automatic/default mapping generation; restructured guidance to require manual input and output mapping configuration

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Through documentation paths we hop,
Where optional ways now clearly stop,
Manual mappings, step by step so true,
Clear guidance lights the path for you! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete and lacks most required template sections including Purpose, Goals, Approach, User Stories, Release Notes, Documentation, Training, Certification, Marketing, Automation Tests, Security Checks, Samples, Related PRs, Migrations, Test Environment, and Learning.	Complete the PR description using the required template structure, particularly adding Purpose, Goals, Approach, and other critical sections to provide comprehensive context for reviewers.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: removing statements about automatic input and output mapping generation from documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fixing-issue-1910-main-1766571001

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18cbc34 and 80dcfab.

📒 Files selected for processing (1)

• en/docs/develop/creating-artifacts/data-services/creating-data-services.md

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

en/docs/develop/creating-artifacts/data-services/creating-data-services.md

173-173: Hard tabs
Column: 3

(MD010, no-hard-tabs)

🔇 Additional comments (2)

en/docs/develop/creating-artifacts/data-services/creating-data-services.md (2)

173-226: Input mapping section clearly directs manual configuration.

The restructured section now explicitly guides users through manual input mapping creation with clear step-by-step instructions. The change removes any implication that mappings are automatically generated from the SQL query.

---

239-279: Output mapping section clearly directs manual configuration.

The section now explicitly instructs users to manually add output mappings with detailed steps and examples. The language "To manually add the output mappings" unambiguously clarifies that this is a required manual process, not automatic.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Replace hard tabs with spaces (MD010 violation).

The indentation at line 173 uses hard tabs instead of spaces. Convert to spaces for consistency with Markdown linting standards.

🔎 Proposed fix

~
-2.	To add a new input mapping:
+2.  To add a new input mapping:

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	2. To add a new input mapping:
	2. To add a new input mapping:

🧰 Tools

🪛 markdownlint-cli2 (0.18.1)

173-173: Hard tabs
Column: 3

(MD010, no-hard-tabs)

🤖 Prompt for AI Agents

In en/docs/develop/creating-artifacts/data-services/creating-data-services.md
around line 173, the line "2.	To add a new input mapping:" uses a hard tab for
indentation; replace the hard tab with spaces (use consistent spaces—e.g., 4
spaces or match surrounding file indentation) so the numbered list uses spaces
only and the MD010 lint violation is resolved.