Refactor pdt type resolution from switch to if-else chains

[devdinc]

Summary by CodeRabbit

• Refactor
  • Restructured internal type resolution logic while maintaining existing functionality and behavior.

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

[coderabbitai]

Walkthrough

The pdt type resolution logic in pdc.sk was refactored from a switch expression to a sequence of if-else conditional branches. The type mappings and default behavior remain functionally identical.

Changes

Cohort / File(s)	Summary
PDT type resolution refactor scripts/libs/pdc.sk	Changed control flow from switch-based mapping to explicit if-else chains for resolving pdt types (1→STRING, 2→INTEGER, 3→LONG, 4→FLOAT, 5→DOUBLE, 6→BYTE, 7→SHORT, 8→BOOLEAN), with default fallback to {_none}

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately describes the main change: refactoring pdt type resolution from switch to if-else chains, which aligns with the actual modifications in scripts/libs/pdc.sk.

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

✨ 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 Remove-skbee-depend

---

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.}