fix: prevent TypeError when parsing null object in CLI (#153)

[2k33cse992574]

Fixes appwrite/sdk-for-cli#153

Re-opening this PR from #1662 because the Git commit history of the original branch became orphaned during a force-push.

This PR prevents a TypeError in the CLI parsing logic and includes ONLY the targeted null-guards in templates/cli/lib/parser.ts as requested by the maintainers.

[greptile-apps]

Greptile Summary

This PR adds two null-safety guards to templates/cli/lib/parser.ts to prevent TypeErrors when the CLI parser encounters null values in API responses.

• Adds if (obj == null) return result; at the top of filterObject so that null values passed through filterData's array-mapping path no longer throw a TypeError: Cannot convert undefined or null to object.
• Replaces the first-element-only typeof section.value[0] === "object" heuristic with section.value.some(item => item !== null && typeof item === "object"), correctly routing arrays that start with null but contain real objects into drawTable rather than drawScalarArray.

Confidence Score: 5/5

The changes are minimal, targeted null-safety guards with no new logic paths or side effects.

Both changes are straightforward defensive guards: the filterObject early return on null is harmless (the existing caller already avoids passing null, so this is pure defense-in-depth), and the .some() replacement correctly handles arrays whose first slot is null while drawTable already tolerates null entries via toJsonObject(maskedItem) ?? {}.

No files require special attention.

Important Files Changed

Filename	Overview
templates/cli/lib/parser.ts	Two targeted null-safety fixes: null guard in filterObject and replacement of first-element heuristic with .some() scan for mixed/null-leading arrays

_{Reviews (2): Last reviewed commit: "fix: use some() and == null for parser h..." | Re-trigger Greptile}