fix: ParseGeoPoint longitude validation checks wrong variable

[Copilot]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Closes: #1007

Approach

ParseGeoPoint longitude validation was checking latitude instead of longitude, allowing invalid coordinates like (0.0, 200.0) to pass while incorrectly rejecting valid latitudes in range [90, 180).

Fix:

• Changed latitude to longitude in the two longitude bound assertions

// Before (incorrect)
assert(latitude < 180, 'Longitude must be within the range (-180.0, 180.0).');
assert(latitude > -180, 'Longitude must be within the range (-180.0, 180.0).');

// After (correct)
assert(longitude < 180, 'Longitude must be within the range (-180.0, 180.0).');
assert(longitude > -180, 'Longitude must be within the range (-180.0, 180.0).');

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• dl-ssl.google.com
  • Triggering command: /usr/bin/wget wget -qO- REDACTED (dns block)
• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Longitude validation checks wrong variable</issue_title>
<issue_description>### New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server and the Parse Flutter SDK.

Issue Description

Lines 14-17 and 18-21 validate latitude against longitude bounds instead of validating longitude. This means:

• Longitude is never validated, allowing invalid coordinates like (0.0, 200.0) to pass.
• Valid latitudes in the range [90, 180) would incorrectly fail the assertion.

Apply this diff to fix the validation:

     assert(
-      latitude < 180,
+      longitude < 180,
       'Longitude must be within the range (-180.0, 180.0).',
     ),
     assert(
-      latitude > -180,
+      longitude > -180,
       'Longitude must be within the range (-180.0, 180.0).',
     );

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

      assert(
        longitude < 180,
        'Longitude must be within the range (-180.0, 180.0).',
      ),
      assert(
        longitude > -180,
        'Longitude must be within the range (-180.0, 180.0).',
      );

🤖 Prompt for AI Agents

In packages/dart/lib/src/objects/parse_geo_point.dart around lines 14 to 21, the
two assertion checks are incorrectly validating the variable latitude against
longitude bounds; change both assertions to validate longitude instead (i.e.,
assert(longitude < 180, 'Longitude must be within the range (-180.0, 180.0).')
and assert(longitude > -180, 'Longitude must be within the range (-180.0,
180.0).')), leaving the messages intact so longitude is actually validated and
latitude assertions remain correct elsewhere.

Comments on the Issue (you are @copilot in this section)

• Fixes Longitude validation checks wrong variable #1053

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.51%. Comparing base (ec4eaa1) to head (e9eebc2).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1089      +/-   ##
==========================================
+ Coverage   43.40%   43.51%   +0.11%     
==========================================
  Files          61       61              
  Lines        3587     3587              
==========================================
+ Hits         1557     1561       +4     
+ Misses       2030     2026       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[parseplatformorg]

🎉 This change has been released in version dart-v9.4.1