fix: use delete method for unarchive module

[Prashant-Surya]

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

• Bug Fixes

  • Corrected module unarchive operation to use proper HTTP protocol and API resource path.

• Chores

  • Version bumped to 0.2.2.

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

[coderabbitai]

Walkthrough

Version bumped from 0.2.1 to 0.2.2 in package.json. The unArchiveModule API method refactored to use DELETE request instead of POST and updated endpoint path to /archived-modules/ resource.

Changes

Cohort / File(s)	Change Summary
Version Update package.json	Version field updated from 0.2.1 to 0.2.2
Module Archival API Refactor src/api/Modules.ts	unArchiveModule HTTP method changed from POST to DELETE; endpoint path updated from /modules/{mid}/unarchive/ to /archived-modules/{mid}/unarchive/ to align with archived-modules resource

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Specific areas requiring attention:
  • Verify that the DELETE method change doesn't break existing API compatibility or client expectations
  • Confirm the new /archived-modules/ endpoint path is correctly implemented server-side
  • Check if any tests or documentation reference the old POST method and need updating

Poem

🐰 A version hops from two-to-one to two-to-two,
Archived modules now use DELETE (who knew?).
Old POST requests retire with grace,
REST principles win the race! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: switching the HTTP method for the unarchiveModule function from POST to DELETE, which aligns with the file-level changes in src/api/Modules.ts.
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
• Commit unit tests in branch feat/v0.2.2

---

📜 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 c27d4cf and 37f1280.

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/api/Modules.ts (1 hunks)

🔇 Additional comments (2)

package.json (1)

3-3: LGTM!

Patch version bump is appropriate for this bug fix.

src/api/Modules.ts (1)

127-131: Approve the API method change; verify alignment with backend API.

The change from POST to DELETE and the updated endpoint path to /archived-modules/ looks appropriate for unarchiving from an archived resource collection. The method signature remains unchanged, so this is not a breaking change for SDK consumers.

Note the asymmetry with archiveModule (line 120-122) which uses POST on /modules/.../archive/. This is likely intentional based on the backend API design, but please confirm this matches the actual API specification.

---

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

[cursor]

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on December 20.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.