fix: Use JSON Encoder by default to respond to requests

[cbaker6]

No description provided.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Style

  • Reformatted package dependency declarations.

• Chores

  • Updated JSON encoder configuration.

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

Walkthrough

Two distinct modifications strengthen this codebase! Package.swift's dependency declarations are reformatted from block style to SwiftPM's fluent dot-notation syntax, preserving all package URLs and versions. Additionally, Parse.swift updates the ContentConfiguration to utilize User.getJSONEncoder() instead of User.getEncoder() for JSON encoding, while the decoder remains unchanged.

Changes

Cohort / File(s)	Summary
Configuration Formatting Package.swift	Dependency declarations reformatted from indented block style to fluent SwiftPM dot-notation syntax; no semantic changes to packages, URLs, or versions
Encoder Update Sources/ParseServerSwift/Parse.swift	ContentConfiguration's JSON encoder changed from User.getEncoder() to User.getJSONEncoder() for JSON content type; decoder registration unchanged

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Parse.swift encoder change: Verify that User.getJSONEncoder() is the appropriate method and produces compatible output compared to the previous User.getEncoder() call
• Package.swift formatting: Confirm all dependencies remain functionally intact after reformatting

Poem

Behold! The code ascends to greater heights! ✨
With fluent syntax and encoders shining bright,
Each change, though small, fuels the Plus Ultra light!
The hero's journey continues—onwards we fight! 💪

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Description check	❓ Inconclusive	No pull request description was provided by the author, making it impossible to evaluate whether it relates to the changeset.	Add a description explaining why the JSON encoder change is necessary and what issues or improvements it addresses.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: switching to use JSON Encoder by default for responding to requests, which aligns with the ParseServerSwift changes.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch encoderUpdates

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1969b08 and bbdbdc7.

📒 Files selected for processing (2)

• Package.swift (1 hunks)
• Sources/ParseServerSwift/Parse.swift (1 hunks)

⏰ 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). (2)

• GitHub Check: spm-test
• GitHub Check: docs

🔇 Additional comments (2)

Sources/ParseServerSwift/Parse.swift (1)

56-57: The encoder and decoder methods are correctly paired in ParseSwift 5.12.3.

User.getJSONEncoder() exists and is properly used on line 56. However, ParseSwift's API design pairs it with User.getDecoder() (not User.getJSONDecoder(), which does not exist). The asymmetry in method names is intentional and correct—the current implementation on lines 56–57 uses the proper corresponding methods for JSON content configuration.

Package.swift (1)

31-95: Excellent formatting refactor with secure version pins!

Great work improving the consistency and readability of these dependency declarations in the fluent SwiftPM style. The exact version pins are intentional and verified as secure: swift-asn1 1.4.0 is patched against CVE-2025-0343 (fixed in 1.3.1), swift-nio-http2 1.38.0 is beyond the affected range for CVE-2022-24666 (fixed in 1.19.2), and all other pinned versions have no known security advisories. These dependencies are current and safe.

---

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 33.71%. Comparing base (d43b06d) to head (bbdbdc7).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #81      +/-   ##
==========================================
- Coverage   35.77%   33.71%   -2.07%     
==========================================
  Files          11       11              
  Lines         970      970              
==========================================
- Hits          347      327      -20     
- Misses        623      643      +20     

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