fix: user settings PATCH treats null body values as field omission

[tmdeveloper007]

fix: user settings PATCH treats null body values as field omission

[vercel]

@TESTPERSONAL is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[Priyanshu-byte-coder]

Two issues:

1. Missing EOF newline on e2e/landing.spec.js.

2. Null allowed into boolean field: Changing guards from typeof is_public === 'boolean' to is_public !== undefined allows { is_public: null } through — null will be assigned to a typed boolean column. Change to is_public !== undefined && is_public !== null to properly handle field omission vs explicit null.