added parser for the spatial types

[ArnabChatterjee20k]

Screencast.from.2025-10-28.09-23-34.webm

Summary by CodeRabbit

• Bug Fixes
  • CSV import now correctly handles Point, Line, and Polygon geometry columns by accepting JSON-encoded string values during row parsing (string values are decoded; non-strings yield null).

[coderabbitai]

Walkthrough

The pull request extends CSV row parsing to handle scalar column types TYPE_POINT, TYPE_LINE, and TYPE_POLYGON. For those types, if the CSV cell value is a string the code now calls json_decode on it; otherwise it yields null. The change is confined to the existing scalar parsing branch in the CSV migration source handler and does not alter other parsing logic or error handling.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Change is localized to a single migration-related file with a small conditional addition.
• Pattern is repetitive and straightforward: type checks plus a json_decode call.
• Low logic density and minimal surface area for regressions.

Areas requiring attention:

• Confirm the constant names (TYPE_POINT, TYPE_LINE, TYPE_POLYGON) match declarations used elsewhere.
• Verify expected JSON formats for point/line/polygon values and that json_decode error handling (or lack thereof) is acceptable.
• Ensure null fallback behavior aligns with existing semantics for empty/invalid geometric values.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "added parser for the spatial types" directly aligns with the main change described in the raw summary, which adds handling for spatial column types TYPE_POINT, TYPE_LINE, and TYPE_POLYGON during CSV row parsing. The title is concise, specific, and clearly communicates the primary change without unnecessary details or vague language. A teammate reviewing the repository history would immediately understand that this PR introduces parsing functionality for spatial data types.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dat-828

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between be4443a and 974d352.

📒 Files selected for processing (1)

• src/Migration/Sources/CSV.php (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/Migration/Sources/CSV.php

---

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: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f5c1d2c and be4443a.

📒 Files selected for processing (1)

• src/Migration/Sources/CSV.php (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

src/Migration/Sources/CSV.php (1)

src/Migration/Resources/Database/Column.php (1)

• Column (8-155)