[swittk]

Pull Request

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

Issue

Parse.serverURL is intended to be accessible in the global Parse scope, however, with the current typing changes, Parse.serverURL would not be accessible without an explicit (import Parse from 'parse') in the same file, due to serverURL not being part of the exported variables in index.d.ts

Approach

Added serverURL to the index.d.ts declaration.

Tasks

Summary by CodeRabbit

• New Features
  • Added serverURL to the public API, allowing users to access and reference server URL configuration directly.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new top-level export serverURL is added to the TypeScript type declarations, exposing the Parse server URL at the module level of the public API surface.

Changes

Cohort / File(s)	Summary
Type Declarations types/index.d.ts	Added public export for serverURL with type signature derived from Parse['serverURL'].

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description explains the problem (serverURL not exported), the solution (adding it to index.d.ts), and acknowledges the template requirements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly and specifically describes the main change: making Parse.serverURL accessible via the global Parse scope by fixing its export in the type declarations.

_{✏️ 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

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (8c96da9) to head (503d4b9).
⚠️ Report is 12 commits behind head on alpha.

Additional details and impacted files

@@            Coverage Diff            @@
##             alpha     #2917   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         6235      6235           
  Branches      1477      1481    +4     
=========================================
  Hits          6235      6235           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[parseplatformorg]

🎉 This change has been released in version 8.1.1-alpha.6

[parseplatformorg]

🎉 This change has been released in version 8.2.0