fix: Parse Server option rateLimit.zone does not use default value ip

[mtrezza]

Pull Request

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

Issue

Parse Server option rateLimit.zone does not use default value ip. Due to typos in the code comment the parser doesn't recognize the default value.

Approach

Fix code comment.

Summary by CodeRabbit

• New Features

  • Rate limit zone configuration now has an explicit default value ("ip").

• Documentation

  • Rate limit option help text reformatted from inline HTML breaks to semantic bulleted lists and now notes the default clearly.

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

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[coderabbitai]

📝 Walkthrough

Walkthrough

Added an explicit default value 'ip' to RateLimitOptions.zone and reformatted rate-limit help text from HTML line breaks to semantic unordered lists across three option files.

Changes

Cohort / File(s)	Change Summary
RateLimit Options — Definitions src/Options/Definitions.js	Added default: 'ip' to RateLimitOptions.zone; help text reformatted from HTML <br> breaks to an unordered list.
RateLimit Options — Documentation src/Options/docs.js	Reformatted RateLimitOptions.zone documentation from inline HTML breaks to a semantic unordered list and added a concise "Default is ip." note.
RateLimit Options — Index/Comments src/Options/index.js	Reformatted rate-limit descriptive comment from HTML <br> formatting to a bulleted list and annotated default as :DEFAULT: ip (documentation/comment-only change).

Sequence Diagram(s)

(omitted) — changes are documentation/default-value only; no control-flow modifications to illustrate.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5–15 minutes

• Verify default: 'ip' is intended and consistent with runtime expectations.
• Confirm documentation text preserves original meanings and formats correctly in all three files.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is missing the required 'Closes' issue link and incomplete task checklist; it only provides minimal explanation without issue details.	Add the issue link in the 'Closes:' field and complete or update the tasks checklist to reflect the actual work performed in this PR.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing the Parse Server option rateLimit.zone to use its default value ip by correcting code comments.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8860b73 and 552c578.

📒 Files selected for processing (3)

• src/Options/Definitions.js (1 hunks)
• src/Options/docs.js (1 hunks)
• src/Options/index.js (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/Options/Definitions.js

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-08T13:46:04.940Z
Learning: When reviewing Parse Server PRs that add new features, always check whether the feature is documented in the README.md file, though for new Parse Server options this is optional rather than required.

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-17T15:02:48.786Z
Learning: For Parse Server PRs, always suggest an Angular commit convention PR title that would make a meaningful changelog entry for developers. Update the PR title suggestion on every commit. The format should be: type(scope): description. Common types include feat, fix, perf, refactor, docs, test, chore. The scope should identify the subsystem (e.g., graphql, rest, push, security). The description should be action-oriented and clearly convey the change's impact to developers.

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-08T13:46:04.940Z
Learning: For new Parse Server options, verify that the option is documented in src/Options/index.js and that npm run definitions has been executed to reflect changes in src/Options/docs.js and src/Options/Definitions.js. README.md documentation is a bonus but not required for new options.

📚 Learning: 2025-11-08T13:46:04.940Z

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-08T13:46:04.940Z
Learning: For new Parse Server options, verify that the option is documented in src/Options/index.js and that npm run definitions has been executed to reflect changes in src/Options/docs.js and src/Options/Definitions.js. README.md documentation is a bonus but not required for new options.

Applied to files:

• src/Options/docs.js
• src/Options/index.js

🪛 Biome (2.1.2)

src/Options/index.js

[error] 373-373: Expected a statement but instead found '?'.

Expected a statement here.

(parse)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: Benchmarks
• GitHub Check: Node 18
• GitHub Check: PostgreSQL 15, PostGIS 3.4
• GitHub Check: MongoDB 8, ReplicaSet
• GitHub Check: Node 22
• GitHub Check: MongoDB 6, ReplicaSet

🔇 Additional comments (3)

src/Options/docs.js (1)

125-125: LGTM! Documentation formatting improved.

The reformatting from HTML line breaks to a semantic unordered list improves readability and follows modern documentation practices.

src/Options/index.js (2)

373-382: Static analysis false positive.

The Biome parsing error on line 373 is a false positive. The ? character is part of Flow's optional type syntax (?string on line 382), which is valid Flow notation for nullable/optional types.

---

373-382: LGTM! Critical fix verified and properly propagated.

The :DEFAULT: ip annotation on line 381 of src/Options/index.js has been correctly processed and reflected in src/Options/Definitions.js. The zone property now includes default: 'ip' with updated documentation matching the HTML list format. Verification confirms npm run definitions was executed as required for Parse Server option changes.

---

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

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.51%. Comparing base (38c9d2e) to head (8860b73).

❗ There is a different number of reports uploaded between BASE (38c9d2e) and HEAD (8860b73). Click for more details.

HEAD has 10 uploads less than BASE

Flag	BASE (38c9d2e)	HEAD (8860b73)
	11	1

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha    #9941      +/-   ##
==========================================
- Coverage   93.08%   84.51%   -8.57%     
==========================================
  Files         187      187              
  Lines       15275    15275              
  Branches      177      177              
==========================================
- Hits        14219    12910    -1309     
- Misses       1044     2353    +1309     
  Partials       12       12              

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.08%. Comparing base (50edb5a) to head (552c578).
⚠️ Report is 3 commits behind head on alpha.

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha    #9941      +/-   ##
==========================================
- Coverage   93.09%   93.08%   -0.01%     
==========================================
  Files         188      188              
  Lines       15298    15298              
  Branches      177      177              
==========================================
- Hits        14241    14240       -1     
- Misses       1045     1046       +1     
  Partials       12       12              

☔ 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.5.0-alpha.14